BookmarkSubscribeRSS Feed

What’s the deal with beacon, click, and action count URLs in SAS Intelligent Advertising for Publishers?

Started ‎12-22-2015 by
Modified ‎12-22-2015 by
Views 978

In SAS Intelligent Advertising for Publishers, actions are sent to the system using the 'count' directive.

For example:

 

http://{SASIA adserver URL}/{customer short name}/{content type}/count/fcid=1234/act=3/inc=1

 

- increments the action count for fcid 1234 [the unique creative identifier] by 1.

act=1 This ad call parameter denotes a beacon count URL.

act=2 This ad call parameter denotes a click count URL. When using this instead of the 'adclick' directive the click count is incremented but the browser is not relocated to the click URL destination.

act=3 This ad call parameter denotes a generic action count URL.

inc=X This ad call parameter increments the count by X

When act= is missing, 1 is assumed. When inc= is missing, 1 is assumed.

Other targeting tags present in the URL [site or area, for example] will be logged against when the URL is executed. Note that the current version of action tracking is not cookie-based, hence the need for the FCID value to be present in the URL for correct counting.

 

Check Usage Note 53313: Beacon, Click, and Action Count URLs in SAS Intelligent Advertising for Publishers for updates to this information.

Contributors
Version history
Last update:
‎12-22-2015 03:42 PM
Updated by:

hackathon24-white-horiz.png

2025 SAS Hackathon: There is still time!

Good news: We've extended SAS Hackathon registration until Sept. 12, so you still have time to be part of our biggest event yet – our five-year anniversary!

Register Now

SAS AI and Machine Learning Courses

The rapid growth of AI technologies is driving an AI skills gap and demand for AI talent. Ready to grow your AI literacy? SAS offers free ways to get started for beginners, business leaders, and analytics professionals of all skill levels. Your future self will thank you.

Get started

Article Tags