Amazon Ad Server Post-Click ID
Adding the Ogury Post-Click ID to the final landing Page URL helps us to properly retrieve and optimize post-click KPIs for Amazon Ad Server campaigns, without using third party cookies.
Furthermore, this ID ensures that our Post-Click tracker accurately tracks the actions of a user that arrives to your landing page once they click from your ad.
How to add Post-Click ID in Redirect
This process requires action from the client setting up the AAS placement (documentation can be found here).
For each Ogury’s placement tracking, the client adds &ogypcl=[postclick_id] in the AAS' Line ID field
Finally, the client adds the Ogury Post-Click ID query parameter ogypcl= and the [%tp_LineID%] token as below :
if the final landing page DOES NOT integrate UTM parameters, the client appends the ?ogypcl=[%tp_LineID%] token at the end of each Ogury placement clickthrough URL
if the final landing page DOES integrate UTM parameters, the client appends the &ogypcl=[%tp_LineID%] token at the end of each Ogury placement clickthrough URL
Set-up example with no UTM on landing page
Set-up example with UTM on landing page
The AAS Display redirect goes through several hoops before reaching the actual landing page URL. If the final landing page DOES integrate UTM parameters, it's mandatory to encode both the UTM and Ogury Post-Click ID query parameters as below to complete the clickthough URL field. This will prevent the UTM characters from cutting off.
All the client set up detailed above must be done before publishing the AAS tags so that the Line ID parameter will be automatically added to the tag upon tag generation.
Example of a compliant generated AAS Display Redirect Tag below. The double-dollar symbols $$ enclosing the value passed in the LineID parameter cannot be removed. Removal will cause the click tracking URL to be broken.
<script src="https://bs.serving-sys.com/Serving/adServer.bs?c=28&cn=display&pli=XXXXXXX&gdpr=${GDPR}&gdpr_consent=${GDPR_CONSENT_68}&us_privacy=${US_PRIVACY}&w=520&h=867&ord=[timestamp]&LineID=$$[postclick_id]$$&z=0"></script> <noscript> <a href="https://bs.serving-sys.com/Serving/adServer.bs?cn=brd&ns=1&pli=XXXXXXX&gdpr=${GDPR}&gdpr_consent=${GDPR_CONSENT_68}&us_privacy=${US_PRIVACY}&Page=&Pos=-1004972369&LineID=$$[postclick_id]$$" target="_blank"> <img src="https://bs.serving-sys.com/Serving/adServer.bs?c=8&cn=display&pli=XXXXXXX&gdpr=${GDPR}&gdpr_consent=${GDPR_CONSENT_68}&us_privacy=${US_PRIVACY}&Page=&Pos=-1004972369&LineID=$$[postclick_id]$$" border=0 width=520 height=867></a> </noscript>
How to add Post-Click ID in Click Tracker
This process requires action from the client setting up the AAS placement (documentation can be found here).
For each Ogury’s placement tracking, the client adds [postclick_id] in the AAS' Line ID field
Finally, the client adds the Ogury Post-Click ID query parameter ogypcl= and the [%tp_LineID%] token as below :
If the final landing page DOES NOT integrate UTM parameters, the client appends the ?ogypcl=[%tp_LineID%] token at the end of each Ogury placement clickthrough URL
If the final landing page DOES integrate UTM parameters, the client appends the &ogypcl=[%tp_LineID%] token at the end of each Ogury placement clickthrough URL.
All set up must be done before publishing the AAS tags so that the Line ID parameter will be automatically added to the tag upon generation.
The double-dollar symbols $$ enclosing the value passed in the LineID parameter cannot be removed. Removal will cause the click tracking URL to be broken.
Set-up example with no UTM on landing page
Set-up example with UTM on landing page
Last updated
Was this helpful?