CAKE Knowledge Base

How to Manage Event Visibility in the Affiliate Portal Using Publish Events

Updated Jan 08, 2021

This article will cover the following:

  • What are Events and the Publish Setting?
  • How does the Publish Setting Control Visibility in the Affiliate Portal?

What are Events and the Publish Setting?

Events are user actions that can be tracked pre- and post-conversion or application install. They are a great way to track steps within a funnel, free trial signups, in-app purchases, returning customers and so much more. Events can be revenue impacting actions or simply used for gaining insight into customer behavior.

Events can be set to be Publish or Unpublish depending on if you want the Event visible to the Affiliate in the Affiliate portal.

You have the ability to determine the visibility of Conversions/Events in the Affiliate Portal with the Publish  checkbox. By default, when creating an Active Event on the Advertiser card, that Event is set to Publish on the Offer and Campaign cards.  A Publish status can be overridden at the Offer as well as on the Campaign card.

How does the Publish Setting Control Visibility in the Affiliate Portal?

When you Publish a Conversion or Event:

  • Conversion or Event will be displayed in Affiliate Portal reports
  • Affiliate pixel (regardless of Price Paid) will be fired. 

Note: If a Paid disposition is set, it will trump the Publish logic

Checking the “Publish” checkbox at the:

Advertiser Level:  This Event will be visible in Affiliate Reports and CAKE will fire Affiliate pixels by default for all Offers/Campaigns on which the Event is Active. Uncheck this box on the Offer card/Offer Contract tab to adjust for specific Offers/Contracts.

Offer Level: this Event will be visible in Affiliate Reports and will fire Affiliate pixels by default for all Affiliates running this particular Offer. Unpublish on the Campaign card to adjust for specific Affiliates/Campaigns.

Campaign Level: Only this Affiliate on this Offer will see this Event in their Reports and their pixel will be fired.

Unpublish

When you unpublish a Conversion or Event:

  • Conversion or Event will not show in Affiliate Portal reports
  • CAKE will not fire any associated Affiliate pixel
  • The Price Paid will be set to $0 automatically
  • Your Admin reports will continue to display these Conversions/Events

Unchecking the “Publish” box at the:

Advertiser Level: this Event will not be visible to Affiliate Reports nor will CAKE fire Affiliate pixels by default for all Offers/Campaigns on which it is Activated. Check "Publish" on the Offer card/Offer Contract tab to adjust for specific Offers/Contracts.

Offer Level: this Event will not be visible to Affiliate Reports nor will CAKE fire Affiliate pixels by default for any Affiliates running this Offer. Check "Publish" on the Campaign card to adjust for specific Affiliates.

Campaign Level: Only this Affiliate on this Offer will not see this Event in their Reports nor will their pixel will be fired.

FAQ's

What if my instance does not have Events enabled? I don't seem to have access to Publish or Unpublish Conversions.

If your instance does not have Events enabled, CAKE will publish all Conversions by default regardless of price. However, we have released a setting that will enable you to continue to hide $0 conversions from the reports in the Affiliate Portal. Setup tab > Settings > Affiliate Portal Settings > Affiliate Reports section > Hide Zero Conversions:

What if I use dynamic Pricing on RevShares? Will CAKE display $0.00 Conversions/Events when we are not paid?

CAKE has an option in Tracking Setting to choose to Suppress unpaid RevShares.  To enable this go to:

  • Tracking Settings
  • Setup tab
  • Settings
  • Tracking Settings
  • Suppress unpaid RevShares
  • Checking this box will hide all Conversions/Events where the Advertiser sends a ‘0’ on the p= parameter of your pixel for RevShare Offer Contracts only. The Affiliate’s pixel will not be fired.

 

This setting also impacts leads. If it’s a revshare with a price of $0.00 CAKE is not firing the pixel or showing it to the Affiliate.

Will I be able to control the visibility of $0 CPC or CPMs?

No. For CPC Offers, the clicks are the conversions. There is no way to hide clicks from the Affiliate Portal.

For CPM’s, the Conversion happens after an Impression pixel loads 1000 times (“Views” Column in Reporting). Again, there is no way to hide “Views” from the Affiliate Portal.

 

Can I add “Published” Conversions to a Campaign without those Conversions showing up in the Affiliate’s reports?

Yes. When doing a Mass Adjustment to add conversions to a campaign, if you set the Price Paid field to “0”, a dropdown will appear allowing you to select an Unpaid Disposition. Adding an Unpaid Disposition to a conversion/event will hide it from the Affiliate Portal, even if the Event is “Published”.

Is “Unpaid Disposition” available via API/CSV Tools?

Yes. The following API’s have been updated to include this field:

  1. GETdispositions v1 
  2. TrackUpdateConversionEvents v6
  3. TrackMassConversionInsert v3 
  4. TrackMassConversionAdjustment v3 

If you are utilizing Cake’s CSV Conversion Reconciliation Tool, you will need to make sure the templates you use to include the “unpaid_disposition_id” field.

What will happen with past Affiliate portal reports when this is released, will they listen to the setting or to what they were when they happened?

You may have been notified in previous outreach, but conversions before this date (date of release) will use publish setting, after this date, we use the Paid disposition logic of what was with the conversion at the time.

What is the default Publish setting on my Offers and Campaigns?

Checking the “Publish” box at the:

Advertiser Level: this Event will be visible to Affiliate Reports and CAKE will fire Affiliate pixels by default for all Offers/Campaigns on which the Event is Activated. Uncheck this box on the Offer card/Offer Contract tab to adjust for specific Offers/Contracts.

0 Comments

Add your comment

E-Mail me when someone replies to this comment
Previous Article What are Excessive Unique Sub IDs and what to do?
Next Article Chrome v80: Cookie Tracking Updates