
click.linksynergy.com.
To track Rakuten Advertising offers in ClickFlare, two links have to carry the ClickFlare click ID in both directions:
- The offer URL sends the ClickFlare click ID to Rakuten in
u1. - The postback URL sends it back to ClickFlare with every transaction event, together with your commission and Rakuten’s transaction ID. You register it through Rakuten’s Postback API.
u1 needs a feature called Signature on your account, the Postback API is in beta, and Rakuten can send the same sale more than once (a preliminary event, a final event, and a cancellation if the order is returned). This guide covers all of it.
At a glance
To set up Rakuten Advertising with ClickFlare:- Set the domain and reporting time.
- Create two custom conversions.
- Create the Rakuten affiliate network.
- Create the offer with u1.
- Register the postback with Rakuten.
How the data flows
u1 on the way in and returns it in the <u1> field on the way out. Rakuten’s help center writes postback fields in angle brackets, for example is_event=<is_event>.What you’ll need
- An active ClickFlare account with your own tracking domain set up. Shared domains get flagged by networks and blocked by browsers. See Tracking domains.
- A Rakuten Advertising publisher account, approved in the advertiser programs you want to promote.
- Signature enabled on your account. Rakuten makes
u1available to publishers enabled for Signature. Ask your account manager or Rakuten support if you’re not sure. - Access to Rakuten’s Developer Portal (you log in with your Publisher Dashboard credentials), an API access token, and a user account associated with the publisher ID that will use the postback.
- Two custom conversions in ClickFlare, set up in the steps below.
What the Rakuten Advertising template contains
ClickFlare has a Rakuten Advertising affiliate network template. It comes pre-filled with the field names from Rakuten’s own documentation:
{u1}, {sale-amount} and {transaction-id}, with Event Type empty. Open the network and change them to the values above.
Rakuten’s Postback API documentation lives in its Developer Portal, behind a login. The field names above come from Rakuten’s public help center. Before you go live, check them against the Developer Portal’s Events API field list, or ask Rakuten support to confirm the postback format.
Setup
Everything in ClickFlare is done from inside the campaign editor. Create the offer and the affiliate network inline as you go.Set up your own tracking domain
trk.yourdomain.com. The postback URL is built on this domain, so changing it later means registering the postback with Rakuten again. Rakuten skips any endpoint that takes longer than 400 ms to respond, so use a domain that answers quickly. See Tracking domains.Report conversions by postback time
Create two custom conversions
ct value exactly, so enter capital Y and N. A ct value that matches no custom conversion is logged as a general conversion.Create the campaign
Create the Rakuten affiliate network
- Search for Rakuten and pick the Rakuten Advertising template.
- Name it, for example “Rakuten Advertising”.
- Check that Click Id is
<u1>, Payout is<commissions>and Transaction ID is<etransaction_id>, with no spaces before or after. - Check that Event Type is
<is_event>. - Under Conversion tracking, select your own Tracking Domain and keep S2S Postback URL as the tracking method.
- Set Payout currency to the currency Rakuten pays you in.
is_event=<is_event> field in every postback URL, so add it at the end when you copy it:
Build the deep link in Rakuten
id), the advertiser ID (mid) and the destination page (murl):murl is URL-encoded, so the u1 you add next is read as part of the Rakuten link and not as part of the destination.Create the offer in ClickFlare
- Name the offer, for example after the advertiser.
- Select the Rakuten affiliate network you just created.
-
Paste the Rakuten link into Offer URL and turn on Append Click ID to Offer Url. ClickFlare adds
u1={cf_click_id}. You can also add&u1={cf_click_id}yourself. Use one or the other, not both.
u1 value can be up to 72 characters, and Rakuten recommends no special characters. It shows in Rakuten’s reports as the Member ID.Set the payout to Auto so ClickFlare uses the payout value from the postback.Register the postback with Rakuten
Add a lander (optional)
Save the campaign and launch
Preliminary, final and cancelled events
Rakuten can send several postbacks for one sale. Theis_event field tells them apart:
- Preliminary (
is_event=Y). Some advertisers report sales in batches, for example travel and booking sites, pre-orders, or shops that report when the order ships. They send a preliminary event at the time of purchase. Rakuten says to treat everyYevent as preliminary: the advertiser can still remove it. - Final (
is_event=N). When the sale is confirmed, the postback fires again withN. With real-time pixel tracking, theYevent is followed almost immediately by itsNevent. - Cancellation. If the customer cancels or returns the order, Rakuten sends another event with
is_event=N, a negative commission and sale amount, and a new transaction ID. A partial return only carries the returned item’s amount.
etransaction_id, so ClickFlare records each one. That’s why the setup sends is_event as ct:
Rakuten’s postback limits
- 400 ms timeout, one attempt. Rakuten doesn’t send data if your endpoint takes longer than 400 ms, and it doesn’t retry a failed send.
- Postbacks can be disabled without notice. Rakuten says you won’t be told if your postback is disabled automatically. Check it now and then with the Postback API’s endpoint status call.
- Clicks older than 30 days. Rakuten’s Events API keeps click data for 30 days for
u1matching, and transactions from older clicks have nou1. The Postback API pushes the same data, so expect those transactions to arrive without a click ID that ClickFlare can match. - Not for accounting. Rakuten recommends its Signature Reconciliation Feed Reports, not the postback, for reconciling what you’re paid.
Verify the setup
Click through the campaign
click.linksynergy.com. Check that it has u1= followed by a real ClickFlare click ID, not the literal text {cf_click_id}.Test the postback by hand
https://trk.yourdomain.com/cf/cv?click_id=REAL_CLICK_ID&payout=1&txid=test1&ct=N. The conversion should show on the campaign in the Rakuten final column. This tests ClickFlare’s side only.Check the first real transaction
ct set to Y or N.Troubleshooting
Transactions show in Rakuten but not in ClickFlare
Transactions show in Rakuten but not in ClickFlare
- The postback is disabled. Check its status with the Postback API’s endpoint status call.
- Your endpoint was too slow. Rakuten skips endpoints that take longer than 400 ms and doesn’t retry.
- The Member ID is empty in Rakuten. The offer URL is missing
u1={cf_click_id}, Signature isn’t enabled on your account, or the lander CTA links straight to Rakuten. - The click is older than 30 days. Rakuten’s event data may no longer have the
u1for it. - The postback is missing is_event. Rakuten requires
is_event=<is_event>in the URL.
Every sale shows up twice
Every sale shows up twice
Y and N, that only Rakuten final is included in main reporting, and that Event Type is <is_event>.Revenue is far too high
Revenue is far too high
<commissions> and update the postback with Rakuten.ClickFlare receives a literal field name or cf_click_id
ClickFlare receives a literal field name or cf_click_id
- A literal
<u1>or{u1}means Rakuten didn’t replace the field. Confirm the field names and their format with Rakuten support. - A literal
cf_click_idmeans the offer URL in ClickFlare has the token without braces. It must be{cf_click_id}.
FAQ
Does ClickFlare integrate with Rakuten Advertising?
Does ClickFlare integrate with Rakuten Advertising?
Why does Rakuten need Signature for u1?
Why does Rakuten need Signature for u1?
u1 to Signature, its member-level tracking. Without it, u1 isn’t available, and conversions can’t carry the ClickFlare click ID back. Ask your account manager to enable it.Is the Postback API stable?
Is the Postback API stable?
Can I count preliminary events as conversions?
Can I count preliminary events as conversions?
Y events are followed by an N.Can I send the conversion back to my traffic source?
Can I send the conversion back to my traffic source?