Sub ID pricing

This feature provides you with CPC pricing for Sub ID values you have sent to us via the "subId" publisher parameter. Prices are calculated at Sub ID level and you are remunerated accordingly based on the traffic delivered at Sub ID level.

What you need to know

• The Sub ID pricing fields are available in an array in the /feeds/merchants endpoint called "cpcsBySubId"

• Within the "cpcsBySubId" array, you will see an object for each Sub ID value you have provided to us via the "subid" parameter in your traffic.

• It is not enabled by default and must be activated by your account manager

• Sub ID pricing is limited to 100 sub IDs currently. If you send more, only the top 100 in terms of sales and leads will get their own prices.

Under what circumstances is Sub ID pricing available

• If we do not have recent lead data for a given Sub ID, there will be no Sub ID object for it in the array and you should revert to using one of the following:

  • The merchant average values in the parent object

  • The category average values (if available) in the category objects

  • The Links specific values from the /search/link endpoint or the Links Builder in the Publisher Center

  • The Offer-specific values from the /feeds/offers or /search/offers endpoints

• While Sub ID pricing values are presented at merchant level, they are calculated by us at a more granular level. See below for more information on how Estimated CPC values are aggregated.

• The CPCs exposed in the /feeds/merchants endpoint are calculated based on historical traffic data from that Sub ID.

• Sub ID pricing is only available for Flex merchant campaigns

Where can I see pricing by Sub ID?

• Sub ID pricing is only available from the /feeds/merchants endpoint.

• Sub ID pricing is not available from /feeds/offers or /search/offers endpoints.

Sub ID pricing and Links

• When Sub ID pricing is enabled prices for Links will be calculated at sub ID granularity, Links prices are available in the /feeds/merchants endpoint under the cpcsBySubIdForLinks object.

CPC aggregation

At Kelkoo Group CPCs are calculated a very granular level. Where you view Estimated CPC values will dictate the level of aggregation you observe.

When Sub ID pricing is not enabled for you:

• Estimated CPC values are calculated at the following granularity for Offers: Merchant -> Category -> Device -> Offer tier

• Estimated CPC values are calculated at the following granularity for Links: Merchant -> Device

• When viewing Estimated CPCs from within the offer model in the /feeds/offers or /search/offers endpoints, you will be viewing the most granular CPC we can provide - in other words, non-aggregated values.

• When viewing Estimated CPCs from the category array in the merchant feed endpoint, you will be seeing values aggregated at the following granularity: Merchant -> Category -> Device

When Sub ID pricing is enabled for you:

• Estimated CPC values are always calculated in our systems at the following granularity for Offers: Merchant -> Category -> Device -> Offer tier -> Sub ID

• Estimated CPC values are always calculated in our systems at the following granularity for Links: Merchant -> Device -> Sub ID

• When viewing Estimated CPC values within the offer model in the /feeds/offers or /search/offers endpoints, you will be seeing Estimated CPCs that are aggregated and may not exactly reflect your earnings (since our systems still calculate CPCs and pay out to Sub ID granularity)

• When viewing Estimated CPCs from within the cpcsBySubId array in the /feeds/merchants endpoint, you will be seeing values for Offers aggregated at the following granularity: Merchant -> Device -> Sub ID

• When viewing Estimated CPCs from within the directoryLinks array in the /feeds/merchants endpoint, you will be seeing values for Links aggregated at the following granularity: Merchant -> Device. Ensure you use the cpcsBySubIdForLinks array to view the Estimated CPCs at Sub ID granularity: Merchant -> Device -> Sub ID

• In order to ensure the continued usability of the feature, there are no current plans to provide Sub ID pricing at additional granularities.

• With the following example it is easy to see how aggregation is necessary:

  • You deliver traffic across 30 Sub IDs

  • You query the /search/offers endpoint and receive 100 offers in the response

  • For every offer 2 Estimated CPCs are provided per Sub ID (one for desktop devices and one for mobile devices).

  • In this example your response would have 6000 lines just for CPCs.

The below table may assist you in visualising the aggregations:

Given the above, we welcome any feedback you may have on this feature.

Example schema

see cpcsBySubId and cpcsBySubIdForLinks in Merchant feed response format