Skip to main content

Impact Radius - publisher

Updated

Take the offer from Impact Radius

Connect the offer

Go to Campaigns -> My Campaigns page:

ImpactRadius_1.png

Description

Chose the program and find the description that we will use as a description for our offer:

ImpactRadius_12.png

Limitations

All limitations can be found from the actions menu:

ImpactRadius_13.png

ImpactRadius_14.png

Payouts

Payouts can be found on the campaigns page:

ImpactRadius_15.png

Creatives

Creatives can be found from top menu (use filter by campaign) or from the campaign view:

ImpactRadius_16.png

It's possible to download creatives (1), (2) or use the tracking code (3):

ImpactRadius_17.png

Check "Tracking Link" column at the "My Campaigns" page and copy the link clicking onto it:

ImpactRadius_2.png

Creating the new offer in the SLICE Digital Network

Base settings

Offer title and description could be taken from Impact Radius:

ImpactRadius_19.png

ImpactRadius_11.png

  1. We take a tracking link from Impact Radius and set as 'Tracking URL'
  2. We take a tracking link from Impact Radius and set as 'Preview URL'
  3. We add specific parameters to the tracking link to pass required parameters to Impact Radius platform (usually required: affiliate id and transaction ID/click ID)
  4. Macros that can be used in Affise

Required parameters for Impact Radius integration:

  • click ID
  • affiliate ID

It should be passed using macroses {pid} and {clickid} by adding following data to tracking link as 'subId' parameters:

?subId1={clickid}&subId2={pid}

Moreover, we can pass any other parameters to Impact Radius as 'sharedid'. For example:

  • ?subId1={clickid}&subId2={pid}&subId3={geo}&sharedid=[aff_sub: {sub1}|{sub2}|{sub3}|{sub4}|{sub5}; offerid: {offer_id}; time: {time}; ip: {ip}; city: {city}; device_ua: {device_ua}]
  • ?subId1={clickid}&subId2={pid}&subId3={geo}&sharedid={pid}_{clickid}

ImpactRadius_18.png

Landing pages

This settings also should be applied to Landing pages section if exist.

Nothing more need to be changed into Affise. However, there are some parameters that have to be taken from Affise and use into the Impact Radius.

Settings

Offer limitations could be taken from Impact Radius:

ImpactRadius_20.png

Payouts

HasOffers_2.png

This is important to fix all goal ID's as far as it will be specified inside Impact Radius postbacks/pixels.

Conversion limits

Depends of contract.

Affiliates

Enable/disable connected affiliates:

ImpactRadius_21.png

Landing pages

Adding landing page if required. See the links section above.

Creatives

Download creatives from Impact Radius and upload it into SLICE Digital network:

ImpactRadius_22.png

Other settings

HasOffers_3-1.png

The most important parameter here is "Hash password". This parameter is used to authorize postback from Impact Radius.

Setup tracking

SLICE Digital

Take postback from the offer:

ImpactRadius_23-1.png

Don't forget to check goal IDs above (section Payouts) - these values will be used for postbacks:

ImpactRadius_24.png

The basic postback looks like:

Affise Postback
https://offers.slice.digital/postback?clickid=CLICK_ID&secure=SECURE_CODE&action_id=ORDER_ID&sum=ORDER_AMOUNT&status=STATUS_ID&goal=GOAL_ID

We will insert the proper parameters from Impact Radius below.

Impact Radius

Impact Radius provides Postbacks for tracking back. It can be found under Actions column inside dropdown menu:

ImpactRadius_3.png

There is a button "Add Postback":

ImpactRadius_4.png

Check action we need to track using postback and set up postback URL (using GET method):

ImpactRadius_5.png

Macros/parameters that can be used to pass information from Impact Radius

Optional URL Parameters

The URL can include the value of various parameters. Simply include the placeholder for the parameters in the URL. Prior to calling the URL, the placeholders for the parameters will be replaced with their values.

For example if you wanted to populate the campaign name in the URL you would set it up as follows "http://www.domain.com?campaignName={CampaignName}". When the URL is called {CampaignName} would be populated with the value provided.

{CampaignId} Campaign ID
{ActionTrackerId} Action Tracker ID
{MediaPartnerId} Media Partner ID
{CampaignName} Campaign Name
{ActionTrackerName} Action Tracker Name
{MediaPartnerName} Media Partner Name
{ActionId} Action ID
{Status} Action Status
{StatusDetail} More details about the action status, for example the reason for an action modification
{AdId} Ad ID
{Payout} Action payout to the media partner, in the advertiser currency.
{DeltaPayout} The change of the Payout Amount
{IntendedPayout} The intended Payout Amount for an overlimit action
{Amount} Action amount, in the network's currency. Only applicable for sale actions.
{DeltaAmount} Corrected Amount from previous action.
{IntendedAmount} The intended Sale Amount for an overlimit action
{Currency} Currency for the action
{OriginalCurrency} Original currency for the action
{EventDate} The date of when the conversion took place
{CreationDate} The date the action is created in the system
{LockingDate} Date, in network timezone, when the action will be locked.
{ClearedDate} Date, in network timezone, when the action will be cleared.
{ReferringDomain} Domain where the referral took place (if online)
{LandingPageUrl} Url of landing page (if online)
{CustomerArea} Customer Area, derived from IP address
{CustomerCity} Customer City, derived from IP address
{CustomerRegion} Customer Region, derived from IP address
{CustomerCountry} Customer Country Code, derived from IP address
{SharedId} A value that a media partner can include in the click URL which becomes available to your advertisers
{SubId1} Value that a media partner can include in the click URL
{SubId2} Another value that a media partner can include in the click URL
{SubId3} Another value that a media partner can include in the click URL

Item-level parameters

"items" is a collection of item data. Each item has "cat", "sku", "qty", "amt", "rbt", "name".

"join" is function that takes 3-5 arguments, first is the collection, second is a symbol to bind to each value in the collection, third is the expression to compute for each member of the collection, fourth is the optional separator between each expression (default is comma), fifth is an optional leadin, which will be present only if there is data in the collection. Examples assuming 3 items with SKUs GH23, UT66 and RW87 respectively.

Expression
Result
{join(items, i, "sku{i}={i.sku}", "&", "?")} ?sku1=GH23&sku2=UT66&sku3=RW87
{join(items, i, "cat{i}={i.cat}", "&", "?")} ?cat1=Watches&cat2=Shoes&cat3=Hats
{join(items, i, "qty{i}={i.qty}", "&", "?")} ?qty1=3&qty2=4&qty3=11
{join(items, i, "amt{i}={i.amt}", "&", "?")} ?amt1=2.92&amt2=99.32&amt3=4.99
{join(items, i, "rbt{i}={i.rbt}", "&", "?")} ?rbt1=1.00&rbt2=5.00&rbt3=1.50
{join(items, i, "name{i}={i.name}", "&", "?")} ?name1=1.00&name2=5.00&name3=1.50

Postback

Chose "Postback URL" from the dropdown menu (5) and paste following code:

Affise Postback
https://offers.slice.digital/postback?clickid={SubId1}&action_id={ActionId}&sum={Amount}&status=2&goal=sale&secure=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

There are required parameters from Affise:

  • clickid={aff_sub} - check Affise tracking link. Make sure that {clickid} passed by aff_sub (aff_sub={clickid}). Otherwise, change {aff_sub} to parameter that was used instead.
  • goal - goal ID
  • secure - security authorization hash/password
  • sum - order amount (required for sale goals)
  • status - conversion status. Possible statuses:
    • 1 – action is «approved» (paid by advertiser);
    • 2 – action is «pending» (decision in process, request status later);
    • 3 – action is «declined» (not paid by advertiser);
    • 4 – requested action «does not exist» (requested ID is not registered on advertiser's site);
    • 5 - action is «approved» and put on Hold (will be paid by advertiser at a certain amount of time).

Other parameters are no required but good to have. So if you want to get more parameters than use this code instead of the previous one (it includes all available parameters that will be passed as a "comment" and "device_id"):

Affise Postback
https://offers.slice.digital/postback?clickid={SubId1}&action_id={ActionId}&sum={Amount}&status=2&goal=sale&secure=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx&referrer={ReferringDomain}&comment="[From Affise: {SharedId}; CampaignId: {CampaignId}; ActionTrackerId: {ActionTrackerId}; MediaPartnerId: {MediaPartnerId}; CampaignName: {CampaignName}; ActionTrackerName: {ActionTrackerName}; MediaPartnerName: {MediaPartnerName}]"

Testing

You need generate clickid for a test using your affise tracking link. After that, you could test the postback:

ImpactRadius_6.png

On the following page you need to specify your action_id (this is order number - should be unique. Use for a test something like test01, test02 or t01), clickid, goal name and order amount (sum):

ImpactRadius_7.png

Test results should be "HTTP Code: 200" and "HTTP Response: Status: 1":

ImpactRadius_8.png

If you are trying to test with the same action_id - it has "status: 2 - conversion exists". Just change action_is and try again:

ImpactRadius_9.pngIf you are trying to test without setting clickid - it has "status: 2 - Missing mandatory parameter clickid". Just put correct clickid and try again:

ImpactRadius_10.png

Related articles

Powered by Zendesk