Offers - Home Tab
This document will review all of the sub tabs within the Home tab of the Offer card.
Home Tab Items
1) This is the name of that Offer that can be changed in the Name field within the Info sub-tab.
2) The Offer card allows you to navigate to other main entities in the system. Clicking on the hyperlink will open the respective card for either the Vertical or Advertiser. This area will also display currency (if enabled), Price Format and Offer Type.
3) The Upload Thumbnail button allows you to display an image that represents the offer. This will be displayed on the Offer card within the Admin Portal and the Affiliate Portal. This will also link out to the Preview Link, if you have one set.
4) This is the Offer ID that can be referenced in various areas of the platform, such as within the search bar.
5) Clicking the Pixel button will generate a conversion or Event pixel.
6) Clicking the Test button will launch a new browser window that will allow you to test the offer. You must then click the test link, complete the conversion flow and return to the test page to verify the conversion was stored successfully.
7) CAKE has an optional feature called Grouped Offers. When enabled, the Offer card will display a "Generate 1:Many Link" which will allow you to link several offers together for attribution purposes.
Name: The name of the offer can be changed at any time. This will not affect tracking.
3rd Party Name: This is an optional field that must be enabled (not displayed in image above). It is often used when working with a third party system that uses a different offer name. This value will be returned through the offer API request.
Vertical: The Vertical can be changed at any time. Changing the Vertical for an offer could alter the redirect strategy, because a Redirect Offer can be set at the Vertical-level.
Landing Page: This field has two separate items. The first is for Landing Page Name, which can be created on the Offer Card > Landing Pages tab. For each Landing Page Name, there is a corresponding Landing Page URL, which is displayed in the dotted-line box immediate below Landing Page Name. It contains the redirect link provided by the advertiser and allows for CAKE tokens to be used to dynamically send values such as Affiliate ID and Sub IDs to the advertiser. If you need to add a new Landing Page or edit the existing one, you can do so by clicking on Add or Edit.
Redirect Parameters: This field allows you to enter parameters with CAKE tokens that will be appended to the end of the Landing Page URL. The most common use of this feature is CAKE-to-CAKE deep linking and would be used to ensure parameters are sent to the destination landing page. This field supports all tokens that work on a Landing Page and if you are using #ckmrdr# in your Landing Page URL, CAKE will URL-encode the Redirect Parameters. Please see examples below for how CAKE handles parameters and token replacement.
Confirmation Page: This is the location where users will be sent post-conversion. Users who click on the same offer within the defined Click Cookie Days will be redirected to the Confirmation Page if an Upsell Offer is not defined.
SSL: Enabling this feature will generate a secure conversion pixel for this offer, force the affiliate to place a secure pixel on the campaign, and will force the consumer to redirect through a secure CAKE tracking link.
Received: This is where you can set the revenue you are receiving from your advertiser for this specific offer.
Default Payout: This is where you can update the default payout for the offer, which will change the displayed price in the Affiliate Portal. Changing the value in this field will NOT affect existing campaigns.
Status: The status of an offer can be changed at any time. Changing an offer from Private, Apply To Run or Public to Private, Apply To Run or Public will not affect an affiliate that already has an active campaign, but changing an Offer to Inactive will prohibit an affiliate that has an existing campaign from opening the Offer card and will redirect traffic to the Offer Redirect, Vertical Redirect or the Global Redirect, depending on the settings in place.
Hidden: Changing an Offer to Hidden will accomplish the following:
- Affiliates with existing campaigns will no longer be able to access the Offer card.
- Affiliates with existing campaigns can still drive traffic to the offer normally.
- Affiliates that do not have an existing campaign will no longer see the offer, even if the offer is set to Public or Apply To Run.
Redirect Parameter Examples
Use the following table to determine how CAKE handles building a safe destination URL:
Click Cap: The Click Cap defines how many clicks this offer can receive before redirecting to the Campaign Redirect, Offer Redirect, Vertical Redirect or Global Redirect depending on settings in place. For example, placing “1,000” will restrict the offer to only receiving 1,000 clicks for the defined period of time before redirecting traffic.
Click Cap Interval: This defines the time period for the Click Cap. For example, if “Daily” is selected, this offer can only receive 1,000 clicks per day. This will reset the following day at midnight. Custom allows for a unique date range to be defined. **Note: Failing to select an interval will create a cap that will never reset.
Send Alert Only: When checked, this will not redirect users once the Click Cap has been reached. It will only send an Alert, if an Alert has been created.
Conversion Cap: The Conversion Cap defines how many paid conversions this offer can receive before redirecting to the Campaign Redirect, Offer Redirect, Vertical Redirect or Global Redirect depending on settings in place. For example, placing “500” will restrict the offer to only receive 500 conversions for the defined period of time. Every click that takes place after the cap is met will be redirected.
Conversion Cap Interval: This defines the time period for the Conversion Cap. For example, if “Daily” is selected this offer can receive 500 conversions per day and will reset the following day at midnight. Custom allows for a unique date range to be defined. **Note: Failing to select an interval will create a cap that will never reset.
Send Alert Only: When checked, this will not redirect users once the Conversion Cap has been reached. It will only send an Alert, if an Alert has been created.
Conversion Cap Behavior: This determines what CAKE should do for conversions that come in after the Cap has been reached, because the user clicked on the offer before the cap had been reached. There are six options:
- Default to Global: Use the setting selected under Setup.
- Advertiser Payment, Affiliate Payment: Charge the advertiser for the conversion & pay the affiliate for the conversion.
- Advertiser Payment, No Affiliate Payment: Charge the advertiser for the conversion & do not pay the affiliate for the conversion.
- Ignore Conversion: Completely ignore any conversion that comes in after the Cap is hit.
- No Advertiser Payment, Affiliate Payment: Do not charge the advertiser for the conversion & pay the affiliate for the conversion.
- No Advertiser Payment, No Affiliate Payment: Do not charge the advertiser for the conversion & do not pay the affiliate for the conversion.
Conversion Behavior On Redirect: On occasion, a consumer can click on a tracking link, then, after click but before the conversion, a change could occur in the system. This change could be an affiliate being set to Inactive, or an IP Address being restricted. In these unique situations, this setting allows you to choose how to handle payment and tracking for the conversion.
Expiration Date: The Expiration Date is chosen by selecting a date from the calendar and a specific time from the drop-down. Once the offer has expired, users will be redirected to the Offer Redirect, Vertical Redirect or Global Redirect, depending on settings in place.
Redirect Offer: This is a drop down containing every Offer that can be selected as the Redirect Offer. In an Offer Redirect situation, users will be redirected to the Offer of choice. If no Offer is chosen, users will be redirected to the Vertical Redirect.
Redirect 404: Checking this box will redirect users directly to a 404 page as opposed to an Offer chosen from the Redirect Offer drop down.
Redirect Domain: This allows you to select a Redirect Domain that will be applied as the tracking link for all Campaigns, unless a redirect domain is specified for the Affiliate directly. This is an optional feature that will appear once redirect domains have been applied to your system.
Conversions From Whitelist Only: If you added Pixel Whitelists, enabling this feature will restrict this Offer to only conversions that have occurred from the IP's that have been whitelisted.
Track Search Terms From Non-Supported Search Engines: CAKE is tracking the search terms that a consumer may have used prior to clicking on the CAKE tracking link. By default, CAKE is receiving search terms from the major search engines such as Google, Yahoo!, etc. Enabling this feature will include additional search engines that may return additional values.
Payment Model: First Touch or Last Touch: Select how you would like to handle attribution for your traffic. First Touch will give payment to the first affiliate that generated the conversion. Last Touch will give payment for the conversion to the last affiliate that generated the conversion.
Click Cookie Days: This sets the number of days that a CAKE cookie will reside on the user's computer after clicking a CAKE tracking link. Changing the Click Cookie Days will not affect users that already have a cookie on their computer. This is set to 30 days by default.
Impression Cookie Days: This sets the number of days that a CAKE cookie will reside on the user's computer after an impression has been generated. Changing the Impression Cookie Days will not affect users that already have a cookie on their computer. This is set to 30 days by default.
Minimum Seconds to Conversion: This feature allows you to set a minimum amount of time for a conversion to occur after clicking a unique link and is used to combat fraudulent conversion attempts.
Conversions From Whitelist Only: When checked, this will block all conversions that are not included in the whitelist (Advertisers main tab > Pixel Whitelist sub-tab).
Enable View Thru Conversions: This option only functions if CAKE is tracking an impression pixel. CAKE will track a conversion for a user that never clicked on a unique link but instead triggered an impression pixel to fire and landed on the page where the conversion pixel was placed. This is also known as "Post Impression" tracking.
Click Trumps Impression: This feature is enabled by default. CAKE will attribute the conversion to the affiliate who generated a click as opposed to the impression. This feature only works if View Thru Conversions are enabled.
Allow Duplicate Clicks: Enabling this feature will disable Click Deduplication, meaning that CAKE will track every click as unique.
Throwout Click Period: This sets the window of opportunity for a consumer to convert once they have clicked on a CAKE tracking link. For the most part, you will use this feature with mobile app tracking, as the tracking mechanisms are slightly different than desktop or mobile browser tracking.
Session Regeneration Seconds: This sets the window of opportunity for a consumer to convert once they have clicked on a CAKE tracking link. For the most part, you will use this feature with mobile app tracking as the tracking mechanisms are slightly different than desktop or mobile browser tracking.
Session Regeneration Type: Some tracking situations require a unique setup, such as tracking an app install. In these situations, traditional cookie tracking or tracking via the Request Session ID is not possible. Instead, CAKE provides an alternative method that allows you to track a conversion via a unique ID passed on the tracking link, or mobile device information. This drop down includes the type of tracking method you wish to use. Selecting s2, for example, will set the offer up to track conversions based upon a unique ID passed in s2 and then returned on the Postback URL.
Ignore Duplicate Transaction IDs.: With this feature enabled, CAKE will only allow conversions to occur with unique Transaction ID values, within the Cookie Day duration.
Cookie Domain: These are independent domains used for specific offers or campaigns. These must be added by CAKE Support. If added, you can select your Alternate Cookie Domain in the drop down.
Postbacks Only: Restrict global offer pixels to server-to-server format only.
Pixel: This is where you can place your Global Offer Pixel, which will be called with every conversion pixel.
Postback URL: This is where you can place your Global Offer Postback, which will be called with every server-to-server conversion.
Postback Delay: This allows you to select a delay period (in ms). This will allow your Global Offer Pixel to fire prior to the Postback URL.
Fire Global Pixel: If checked (and the "Fire Global Pixel By Default" is checked under Settings), CAKE will fire the Global Pixel placed in your system settings in addition to the Global Offer Pixel, if placed. If this is not checked, the Global Pixel will not fire.
Fire Pixel on Non Paid Conversions: If checked, CAKE will fire the Global Offer Pixel anytime a conversion occurs, regardless of whether you pay the affiliate on that conversion.
Fire Global System Pixel: Checking this checkbox will tell CAKE to fire the Global System pixel (placed under Settings) every time a conversion occurs from this offer.
Grouped Offers Tab
Grouped Offers allow you to accept affiliate traffic to a "Parent Offer", and then allow the consumer to redirect through to a "Child Offer". Often times, a parent offer can be a landing page that promotes several different offers.
The Grouped Offers tab will be hidden by default unless you've enabled the Grouped Offers feature under Settings.
Once enabled, you will be able to add or remove offers from here. Select the 'Auto Place Pixel' option if you want CAKE to copy the affiliate's campaign pixel into the child offer. For more information on Grouped Offers, click HERE.
Tags allow you to group multiple offers together that share a common tag for the purpose of viewing custom reports, editing multiple offers or displaying unique search terms in the Affiliate Portal.
The Tags tab allows you to see all the tags associated with the offer, and whether they are visible or not to affiliate's by referencing the red or green dot under the Portal column.
To add a new Tag, simply click 'Add' and either choose an existing Tag or type in a new Tag and click 'Save'.