Submit a Ticket My Tickets
Login  Sign up

How to Configure a Dynamic Offer Postback URL

This article will cover:

What Is A Dynamic Offer Postback URL?

A dynamic offer postback URL is an alternative solution to providing your advertiser with multiple offer-specific postback URL’s.  Typically, a new postback URL is generated per Offer that you create and will contain a hardcoded Offer ID value.


This alternative method leverages a CAKE token that is placed in the advertiser’s landing page to dynamically send the CAKE Offer ID and Request ID as a single value. This enables your advertiser to deploy a single Postback URL for server tracking across multiple offers.

What Is The #oreqid# Token?

#oreqid# is a token that is required when configuring a dynamic offer postback URL. This token combines the Offer ID and Request ID into a single value. When you click on a standard CAKE tracking link, you can see the structure in the Landing Page URL has the Offer ID first, then the Request ID value second, separated by a dash. Because this value includes the Offer ID, it eliminates the need to hardcode the Offer ID (o= parameter) on multiple postbacks.

Example Of The #oreqid# Token Values

Link Type

Example Output
Standard Tracking Link15-335898
Lite Click Link





Lite Click Link with Shorten Request ID EnabledB2701DC7-B528-4532-8401-E952901520C7


The structure of the CAKE Request ID changes when using Lite Clicks and Lite Clicks with Shorten Request IDs. Unlike the Request ID on a Standard Click, Lite Click Request IDs use an encrypted format that intentionally obfuscate the Offer ID or Request ID. You can check the Click Report to ensure the correct offer is being attributed.

Example Of The Dynamic Offer Postback URL Structure


The o= parameter is removed when using a Dynamic Offer Postback. The r= parameter is where the oreqid value must be returned. The e=1 value above is just an example and will change with each Advertiser/event.

How To Configure A Dynamic Offer Setup

To configure a dynamic offer setup, follow these steps:

  1. Ensure the advertiser can capture and store at least 1 dynamic value passed to their landing page(s)
  2. Have the advertiser identify the parameter that will receive the oreqid dynamic value
  3. Add #oreqid# to that parameter on the Offer Redirect Parameters field.
  4. Provide the advertiser with the dynamic offer postback structure (see above)
  5. Run a test to ensure the oreqid value is returned into the r= of the postback


Click_id in the example above is just an example, and not the standard value that your advertiser will use. 


Why can't I just use a Global Advertiser postback with the a= parameter?

    A Global Advertiser Postback that uses a=[Advertier ID] is less accurate for attribution. If a user clicks on multiple of an Advertiser's Offers in the same session before converting, attribution is assigned to the Offer ID that received the last click, even if that was not the Offer the user actually converted on. Oreqid solves this by dynamically passing the correct Offer ID each time the user clicks to a new Offer, even if the session stays the same.

You may also be interested in:

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.