Advertiser feed
The advertiser need to make available a product feed containing all the products that should be possible to show in the dynamic ad. The advertiser also need to arrange for the feed to be updated with new products and that deprecated products are removed.
The minimum of information needed for each product is
- Unique product ID
- Product URL (as shown in the browser when visiting the product)
But we recommend to also include
- Image URL
- Name
- Description
- Price
to be able to create a good looking creative.
In cases where the same product can be reached via different urls the suggested approach is to add that product to the feed as two separate products keeping common data equal between the two products and just replaces the product url and the unique id.
ASX currently support feeds in the following formats: CSV, XML and JSON.
Setup the feed
The feed is setup via Assets -> Advertiser Feed.
| Feed field | Description |
|
|
If the site include parameters that don't is included in the product URL in the feed, they can be excluded here. |
| Encoding | Use UTF8 if unsure. |
|
|
Only used for CSV-feeds and should indicate what character that is used to separate each product field in the feed. |
| In the case of CSV-feeds, the first row often is a header and not a product, use this to indicate if the first row should be skipped | |
| Set this if quotes are used inside the field value |
Image width and height should match the intended size in the ads created for the campaign, in the case these fields are left empty a default size of 128px x 128px will be used.
The preferred interval for syncing the feed is every day.
Advertiser feed parameter mappings
To accurately map the values from the feed to the parameters ASX uses internally a mapping needs to been done and this mapping differs a bit depending on the format the feed uses.
| Bidtheatre column type | Description |
| prod_id | The unique product ID |
| prod_url | The product URL used for matching products |
| img_largest | The image URL that should be used in the ad |
Mappings for CSV-feeds
When the feed is created in ASX just click the columns-link to start the mapping. In CSV-feeds all product data is located on one row separated by some delimiter. Enter the column number on the left hand side and what kind of information the column contains on the right hand side.
Mappings for XML-, RSS- or JSON -feeds
Click the params-link and start by entering a product property from the feed as Name and then what that property should be match to in the Column Type-column. Repeat this for all product properties available in the feed.
Advertiser feed filters
ASX supports filtered targeting based on a particular value on some product property. Create a filter by clicking the Edit filters-link and give the filter a name. Once that is done click the Edit settings-link, choose what column type you want to filter on and what value you want that column type to be.
Retargeting pixel
Once the feed is setup, mapped and correctly synced, a retargeting pixel needs to be placed on all product pages. The retargeting pixel makes it possible to tag product visitors with a cookie keeping track of the products seen by the visitor. The retargeting pixel is created under Cookie Groups-tab in the Supply-section. Just select the desired advertiser feed when creating it and click the code-icon to view the actual invocation code the advertiser must install on their site.
The normal way that BidTheatre maps a visit on the site to a specific product is via the http referer. It is however possible to explicitly provide us with the correct product id as given by the advertiser feed. Just include the productId field when setting up your script.
<!-- /* Cookie Group - DRT */ -->
<!-- /* BidTheatre Cookie Group Invocation Script v1.1 */ -->
<!-- /* Place this cookie group script as the first element in the body tag on the page you want to track. */ -->
<script type="text/javascript" src="https://adsby.bidtheatre.com/js/asx_track.min.js"></script>
<script>
asxtrack.config = {
cookieGroupId: 1,
advertiserFeedId: 2,
productId: 3
};
asxtrack.callCookieGroup();
</script>
Comments
0 comments
Article is closed for comments.