Beacons Best Practices

In this article, you will learn more about some best practices to follow for beacons in your campaigns.

Best Practices

• Ensure activity is always captured: Set beacon tracking method to Always Fires to ensure continuous collection and refresh of data.
  
  
• Beacon Validation: After a beacon is placed, beacon will be automatically validated if it’s firing. Ensure that your beacon is set to Play and Valid, and tracking impressions.
  
  
• Make sure that you are in the right advertiser, as beacon data will only be available in the advertiser it is created in. 
  
  
• Attribution Window: In general, it’s seven days for click through action and 30 days for view through actions, but this should match your third-party trackers to follow the same standard as well.
  
  
• The beacon protocol should match the type of page it is going to be running on. If the page is secure, https should be selected. If unsecure, http is fine.
  If an unsecure beacon is placed on a secure page, there will be browser warning messages resulting in a bad user experience. Secure beacons are able to run on unsecure pages without any issue.
  
  
• When you want a beacon to pass shopping cart information, check the Shopping Cart Value Passed on Beacon checkbox. When you do not want a beacon to send shopping cart information, keep this checkbox unchecked.
• A sale beacon has to be validated to allow a package/line item to spend. A beacon is validated if the Daily Status under the Diagnostics area of the beacon summary shows impressions for the previous days.
• Action cap field enables you to configure the maximum number of actions corresponding to a single impression or click. The action cap field determines how many actions can be attributed to a single user per the last impression served to the user.  If a user is served only one impression, but has two conversion pixel fires, this is counted as one action on the Amobee Platform.
  
  
• To piggyback an Amobee beacon in DCM, you have to copy the entire Amobee beacon in one of two sections:
•  If it's a remarketing beacon, place it in the Default section. This will ensure the Amobee remarketing beacon fires every time the Floodlight tag fires regardless of who drove the click.
• If it's a conversion beacon, place it in the Publisher section. This only allows the Amobee conversion beacon to fire if an Amobee impression or click drove the conversion. This will make action tracking on the Amobee Platform more accurate.
• First-party and third-party data pixels should be created in audiences and not in campaigns
• Any pixels created in Campaigns are automatically available in Audiences. Campaigns uses beacons, which are a subset of pixels.
• If you create a first-party pixel in Audiences and select Amobee as the media provider, the pixel is automatically available within Campaigns.
• If a client-side piggyback is created in Audiences, then a pixel must already exist in Campaigns.
• If a server-side piggyback is created, then you can create a new Campaigns pixel within the Audiences workflow.
• Audiences pixels are parsed differently than Campaigns pixels(i.e.beacons).
• If you plan to collect user data with a pixel and redirect to a landing page, be sure to follow the proper syntax.
• A common error is to have question marks(?) where there should be back slashes(/). Another common mistake is to have equal signs (=) where there should be backslashes (/). Make sure that there are backslashes before and after the url keyword. The following pixel code is correct: http://d.turn.com/r/dd/id/url/http://us.burberry.com/store/womenswear/trench-coats