How to traffic to Adform

Before you start to traffic to Adform there are a few things to consider, including the type of information that will be sent across.

Placements and packages

The behaviour in how these work in Symphony vs. Adform are slightly different. Here are a few examples for your reference:

• Symphony single placement = single line item in Adform.
• Symphony performance package = single line item in Adform. So regardless of how many placements you have within the package, these will not appear in Adform - instead only information held at the package level will trafficked across. 
• Symphony sponsorship package = single line item in Adform. So regardless of how many placements you have within the package, these will not appear in Adform - instead only information held at the package level will trafficked across.
• Placement naming conventions: Due to limitations within the Adform API we can't pass through the line item dimensions - namely the width and height for the placement. We therefore strongly advise that you include this information within the placement naming convention in Symphony to ensure that your adops know which creative to assign to the line item in Adform.

Things to note

Here is a quick summary of the components to take note of before trafficking your campaign.

• Mapping: Sometimes you might see a few error icons appear in your trafficking screen against an item. In order to traffic to Adform the client and publisher/site need to be mapped first. Click here to find out how this works in further detail.
• Campaign name: Adform has 99 character restriction in place, Symphony will automatically truncate the name to fit before trafficking. 
• Line items: All line item start date and end date should be within the campaign start date and end date and will not be allowed to traffic if any item falls outside of campaign period.

What information is trafficked to Adform

Each order within a campaign can contain up to 500 line items in Adform. If an order happens to have more than 500 line items an additional order within the campaign will be created in Adform to accommodate the limit reached. 

All campaign line items are trafficked as 'Direct' buy types in Adform.

In the scenario you are using multiple currencies, the case currency will be pushed to Adform. Only one currency can be selected per campaign in Adform and this is always set as the base currency.

Campaigns with multiple purchase order numbers in Symphony will be concatenated (e.g. PO0001, PO0002) and assigned to the PON or budget field in Adform.

Below is a list of the how the purchase types in Symphony translate in Adform when trafficked across.

Symphony Purchase Type	Adform Purchase Type
CPM	CPM
CPC	CPC
CPA	CPA
CPV	CPA
Fixed	Fixed
Bonus (N)	CPM
Bonus (C)	CPM
CPMv	vCPM
CPListen	CPA
CPDownload	CPA
CPD	CPD
CPPeriod	CPA
CPSession	CPA
CPEngaement	CPA
CPEngagementSession	CPA
CPCDynamic	CPC
CPMDynamic	CPM
CPVDynamic	CPV
CPViewableView	CPV
CPCompletedView	CPV
CPLead	CPA
CPThousandReach	CPA
CPLike	CPA
CPFollower	CPA
CPLanding	CPA
CPInstall	CPA
CPSharePost	CPA
CPActivation	CPA
CPSendOut	CPA
CPLinkClick	CPC
vCPM	vCPM
CPMv60	vCPM
CPMv100	vCPM

If you select the option to pass on the media costs to Adform, these will be displayed as follows:

• Gross amount which is purchase cost in Symphony
• Net amount which is net cost in Symphony
• Agency compensation which is agency fee in Symphony

When it comes to naming conventions please refer to the following:

• Campaign name: these truncate to 99 characters
• Order name: unique identifier + campaign name
• Placement name: placement name (with no character restriction in place)
• Package name: package name (with no character restriction in place)

Below is an outline of the known field mappings for campaign information from Symphony to Adform.

Symphony	Adform	Notes
Client	Advertiser	Uses Symphony client data mapping
Campaign name	Campaign name	Symphony campaign name truncated to 99 characters
Budget	Budget	Adform only supports one currency and budget per   campaign
Base Currency	Currency	The converted base (if needed) currency will be sent over
Campaign Start Date	From Schedule
Campaign End Date	To Schedule
	Sub Type	Defaulted to Display
	Placement View Type	Defaulted to Direct
	Manager ID	Left as-is, no corresponding concept in Symphony
	Co Manager ID	Left as-is, no corresponding concept in Symphony
	Trafficking Type	Left as-is so it will inherit the account Trafficking Type, otherwise can be defaulted to InHouse
	Timezone
Campaign Description	Comment	Truncated to 999 characters
Purchase Order	Purchase Order	Symphony PO numbers concatenated and separated by commas
Mapped back to Symphony from Adform after campaign creation	ovkCampaignId	Auto generated by Adform. Unique identifier of an agency or agency office. Can be used for matching Adform's statistics to Media's data. When missing, defaults to agency setting. Left as-is
	crossDeviceTargetingEnabled	Defines whether cross device targeting is enabled for the campaign. When missing, defaults to false. Left as-is
	commentForReporting
	cookieLifeTime
	visibility
	tracking
	adServing
	marathon
	viewHours (CookieLifeTimeSetings)	Period of time within which a conversion can be correlated with an ad impression a user has seen. Left as-is
	clickHours (CookieLifeTimeSetings)	Period of time within which a conversion can be correlated with a banner a user has clicked. Left as-is
	recentViewSeconds (CookieLifeTimeSetings)	Period of time within which a conversion can be registered as "recent" after an impression. Left as-is
	recentClickSounds (CookieLifeTimeSetings)	Period of time within which a conversion can be registered as "recent" after a click. Left as-is
	firstLevelTime (VisibilitySettings)	Time limit in seconds of first viewability level. Impression is registered as viewable, if banner was visible longer, then specified limit of time, after it was fully loaded. Left as-is
	firstLevelArea (VisibilitySettings)	Area limit in percentage of first viewability level. Impression is registered as viewable, if more then specified limit of banner's area was loaded and visible. Left as-is
	secondLevelEnabled (VisibilitySettings)	Defines whether the second viewability level is enabled. Left as-is
	secondLevelTime (VisibilitySettings)	Time limit in seconds of second viewability level. Impression is registered as viewable, if banner was visible longer, then specified limit of time, after it was fully loaded. Left as-is
	secondLevelArea (VisibilitySettings)	Area limit in percentage of second viewability level. Impression is registered as viewable, if more then specified limit of banner's area was loaded and visible. Left as-is
	thirdLevelEnabled (VisibilitySettings)	Defines whether third viewability level is enabled
	thirdLevelTime (VisibilitySettings)	Time limit in seconds of third viewability level. Impression is registered as viewable, if banner was visible longer, then specified limit of time, after it was fully loaded. Left as-is
	thirdLevelArea (VisibilitySettings)	Area limit in percentage of third viewability level. Impression is registered as viewable, if more then specified limit of banner's area was loaded and visible. Left as-is
	Enabled (TrackingSettings)	When missing for a new campaign, it defaults to the advertiser setting. Left as-is.
	viewThroughEnabled (TrackingSettings)	When missing for a new campaign defaults to true. Left as-is
	conversionAttributionPriority (TrackingSettings)	When missing for a new campaign, efaules to Standard. Left as-is
	orderNumber (MarathonSettings)	Unique order identifier generated by Marathon. Left as-is
	budgetNumber (MarathonSettings)	Unique order identifier generated by Marathon. Left as-is

Below is an outline of the known field mappings for order information from Symphony to Adform.

Symphony	Adform	Notes
	StartDate	Left as-is, should default to campaign start date
	EndDate	Left as-is, should default to end date
Order Id from Adform	Id	Only needed when editing
Campaign name + unique identifier	Name
	Budget	Set to 0 since the combined total of orders needs to be total
	CampaignId	Sym campaign data mapping
	Active	Always true
	rtbSettings
	impressionCapping (rtbSettings)	Array, list of impression capping settings. Left as-is
	Type (Capping)	Specifies capping type. Left as-is
	Impressions (Capping)	Frequency limit in impressions. Left as-is
	Period (Capping)	Specifies the period for which capping settings are defined. Left as-is
	Viewability (Capping)
	Type (CappingPeriod)	Specifies type of period capping = [campaign, days, hours]. Left as-is
	Duration (CappingPeriod)	Period duration (used for hour and day capping periods only). Left as-is

Below is an outline of the known field mappings for line item mapping information from Symphony to Adform.

Symphony	Adform	Notes
Order Id from Adform	OrderId	Symphony Order data mapping (package data mapping)
Symphony site data mapping	MediaUuid	Symphony site data mapping
	MediaSectionUuid
Cost Periods of Package	Schedules
	TagComments
	Labels	Left as-is. Ensure that when re-trafficking to Adforms this is not overwritten
Purchase Type	BookingType	Based on the purchase type translation table
Line Item Name	Name	Package name for Performance Package, Placement Name for the rest
	Leads
Goal	Volume
Purchase Cost	Gross Amount	0 if share cost with adserver is turned off
Net Cost	Net Amount	0 if share cost with adserver is turned off
Agency Commission	AgencyCompensation	0 if share cost with adserver is turned off
	GrossAmount	Left as-is, this is the calculated Purchase Rate
	Net Price	Left as-is, this is the calculated Net Rate
	BrandSafetyEnabled
	AdGapId
	Comment
Start Date	Start (LineSchedule)
End Date	End (LineSchedule)