Skip to main content
7SearchPPC traffic source template 7SearchPPC is a self-serve pay-per-click network. It sells text, native, banner, push, popunder and interstitial traffic, bought on CPC or CPM. This guide sets up 7SearchPPC as a traffic source in ClickFlare. It covers passing 7SearchPPC’s click data into your reports and sending conversions, with payout, back to 7SearchPPC so its stats and your ClickFlare stats agree. You do everything from the campaign editor. The 7SearchPPC traffic source is created inline, without leaving the campaign.

​
At a glance

​
How it works

1

7SearchPPC sends the click

A visitor clicks your ad. 7SearchPPC opens your ClickFlare campaign URL and fills in its macros: the click ID in click_id, the cost in cost, plus the campaign, source, ad format, location, device, OS and browser.
2

ClickFlare stores the 7SearchPPC click ID

ClickFlare saves the value of click_id as the visit’s External ID, records the cost, and redirects the visitor to your lander or offer.
3

The conversion reaches ClickFlare

Your affiliate network or store posts the conversion back to ClickFlare, matched on the ClickFlare click ID.
4

ClickFlare posts it back to 7SearchPPC

ClickFlare fires the 7SearchPPC postback, replacing {external_id} with the stored 7SearchPPC click ID and {payout} with the revenue. 7SearchPPC matches it to the original click and credits it to your account through the Advertiser ID.
The mirror to keep straight: in the campaign URL you write ClickFlare’s parameter (click_id) and 7SearchPPC’s macro ({click_id}). The template does this for you. In the postback URL you write 7SearchPPC’s parameter (visitor_id) and ClickFlare’s token ({external_id}). The name visitor_id is 7SearchPPC’s. It carries the click ID.

​
Before you start

  • Set up your own tracking domain. Run the campaign and the postback on your own custom domain. Shared domains get flagged by networks and blocked by browsers. See Custom Domains.
  • Have an offer ready in ClickFlare, and its affiliate network set up to post conversions back to ClickFlare. See Creating an Offer and Adding an Affiliate Network.
  • Find your 7SearchPPC Advertiser ID. It goes into the postback URL. In your 7SearchPPC advertiser account, it is shown under the Profile icon.
  • Decide which conversion 7SearchPPC should receive. 7SearchPPC does not document separate conversion events. Pick the one action that matters most, usually the sale, and send that.

​
Step 1 – Create the campaign and the 7SearchPPC traffic source

  1. Go to Campaigns and click New.
  2. In Traffic Source, open the dropdown and click + New Traffic Source.
  3. Type 7search in the search box and select the 7SearchPPC template.
  4. Enter a Name, for example 7SearchPPC.
  5. Leave Cost currency on USD unless your 7SearchPPC account is billed in another currency.
The template fills in the Parameters table for you: The 7SearchPPC template's Parameters table in ClickFlare, with 7SearchPPC's macros pre-filled Each tracking field becomes a column you can group reports by. Source ID is the one you will use most. It tells you which publishers convert, so you can block or bid up sources in 7SearchPPC. Ad Format helps when one campaign runs several formats. ClickFlare also detects country, city, device, OS and browser on its own from each visit. The 7SearchPPC rows are still useful: they show what 7SearchPPC saw, which helps when you compare the two reports.
Don’t change or remove the External ID row. Without click_id={click_id} in the campaign URL, ClickFlare has no 7SearchPPC click ID to send back, and 7SearchPPC cannot match any conversion.
To pass more 7SearchPPC data, click Add Parameter, give it a name and parameter, and enter the 7SearchPPC macro as the TS Token. ClickFlare assigns the next free tracking field. Only use macros 7SearchPPC lists for your account.

​
Step 2 – Set up the postback

The postback is what sends conversions to 7SearchPPC. It lives on the traffic source, so every campaign that uses this 7SearchPPC traffic source sends conversions the same way.

​
Get your postback values from 7SearchPPC

  1. Log in to 7SearchPPC as an advertiser.
  2. Open Tracking in the left-side menu. The tracking section shows your Postback URL.
  3. Note your Advertiser ID. It is part of that URL, and it is also shown under the Profile icon.
7SearchPPC’s own URL uses its placeholders CLICK_ID and PAYOUT. You don’t paste it into ClickFlare as is. The template already has the same URL with ClickFlare’s tokens in place of those placeholders.

​
Add it to the traffic source in ClickFlare

  1. Back in the New Traffic Source form, scroll to Passing conversion info to traffic source.
  2. Turn on Traffic source postback URL. The template’s postback appears:
It already sends the click ID ({external_id}) and the payout ({payout}), both as ClickFlare tokens.
  1. Replace REPLACE_WITH_ADVERTISER_ID with your 7SearchPPC Advertiser ID. Compare the result with the Postback URL in your 7SearchPPC Tracking section: apart from the two tokens (7SearchPPC’s CLICK_ID and PAYOUT, ClickFlare’s {external_id} and {payout}), the two should match. If 7SearchPPC shows a different host or parameter names, use 7SearchPPC’s version and swap in the two ClickFlare tokens.
  2. In the dropdown on the left, choose the ClickFlare event that should fire the postback. Keep Conversions to send every conversion. If your final action is a custom conversion (for example purchase), choose that instead.
  3. Click Save. You are back in the campaign editor with the 7SearchPPC traffic source selected.
The Traffic source postback URL switched on, showing the 7SearchPPC template's postback
Replace REPLACE_WITH_ADVERTISER_ID with your own Advertiser ID. If the placeholder stays in the postback, 7SearchPPC cannot tie the conversions to your account, and nothing shows in your 7SearchPPC stats.
The payout value is sent as ClickFlare records it. If your offers pay in a currency other than the one your 7SearchPPC account uses, the numbers will not line up in 7SearchPPC. See Multicurrency in ClickFlare. To learn what each postback token does, see How to Configure a Traffic Source S2S Postback URL.

​
Step 3 – Finish the campaign and copy its URL

  1. Name the campaign.
  2. Set the Cost Model to Not Tracked, so ClickFlare uses the cost 7SearchPPC passes. See Cost.
  3. Choose Redirect or Direct tracking. Redirect is the usual choice for 7SearchPPC.
  4. Click Next and, on Destination, add your lander (optional) and your offer.
  5. Save, open Tracking, select your own tracking domain and copy the campaign URL.
The campaign URL already contains every 7SearchPPC macro from the template, for example click_id={click_id} and source_id={source_id}. If you use a lander, its call-to-action must link to the ClickFlare click URL, not to the offer directly. Otherwise the visit reaches the offer without a ClickFlare click ID, and the conversion cannot be traced back to 7SearchPPC. See Creating a Campaign in ClickFlare.

​
Step 4 – Create the campaign in 7SearchPPC

  1. In 7SearchPPC, go to Campaigns and click Create Campaign.
  2. Choose the ad format and click Start.
  3. Fill in the campaign details: targeting, bidding model (CPC or CPM), bid and budget.
  4. Paste the ClickFlare campaign URL into the Destination URL field.
  5. Click Submit. 7SearchPPC reviews the campaign before it goes live.
Paste the URL exactly as ClickFlare gives it. 7SearchPPC replaces each {...} macro when the ad is clicked. If you edit the macros, the columns arrive empty or with the literal macro text.

​
Step 5 – Test the integration

7SearchPPC has a test conversion tool, so you can check the setup before you spend.
  1. In 7SearchPPC, open Tracking in the left-side menu and go to the Conversion Tracking page.
  2. Click Test Conversion.
  3. Paste your ClickFlare campaign URL as the Destination URL and click Test Conversion again.
  4. On the page that opens, complete the offer the way a real visitor would.
  5. Return to the same 7SearchPPC page. A working setup shows Test Conversions Tracked: 1, or a higher count than before. If it hasn’t changed, wait a few minutes and refresh.
  6. In ClickFlare, go to Logs → Postback Status and filter by the campaign. A successful request to pb.7searchppc.com confirms ClickFlare sent the postback.
If the test conversion shows in ClickFlare but not in 7SearchPPC, open Logs → Postback Status and look at the URL ClickFlare sent. It should contain your Advertiser ID and a real click ID, not REPLACE_WITH_ADVERTISER_ID or an empty visitor_id.

​
Sending one event or several

7SearchPPC does not document an event parameter in its postback. Treat it as one conversion type per account: every postback it receives counts as a conversion.
If your funnel has several steps (lead, then sale), map the postback to the step you want 7SearchPPC to count. Create a custom conversion for that step in ClickFlare and choose it in the event dropdown next to the postback. Earlier steps still show in ClickFlare. They just don’t reach 7SearchPPC.To send a postback only for some conversions, for example only those above a certain payout, use Event filter under the postback to add conditions.
You can click + Another postback URL and send several ClickFlare events to the same 7SearchPPC URL. 7SearchPPC would count each one as a conversion, with no way to tell a lead from a sale. Your conversion rate and CPA in 7SearchPPC would then be wrong. Keep one event unless 7SearchPPC confirms it supports more.

​
Cost

The template passes cost in the URL. The Cost row sends 7SearchPPC’s {cost} macro, which 7SearchPPC describes as the click cost as tracked by the platform. ClickFlare records it as the visit’s cost. On the campaign, set the Cost Model to Not Tracked so ClickFlare uses the cost passed in the URL.
On CPC campaigns, {cost} is the price of the click, which is what ClickFlare needs. 7SearchPPC does not say what {cost} holds on CPM campaigns. After launch, compare the Cost column in ClickFlare with your 7SearchPPC spend. If they don’t match:
  • For popunder and interstitial traffic, one impression is roughly one visit. Switch the Cost Model to CPC and enter your CPM bid divided by 1,000 as the cost value.
  • For banner, native, text and push bought on CPM, many impressions lead to one click, so a per-visit cost can’t be derived from the bid. Correct the spend with a manual cost upload.
ClickFlare has no cost-tracking API integration for 7SearchPPC. When the recorded spend differs from your 7SearchPPC spend, correct it with a manual cost upload. See Cost Models.

​
Delayed revenue

If you run search arbitrage (RSOC or AFD) behind 7SearchPPC, the feed reports revenue hours or days after the click. To pass that revenue to 7SearchPPC once it arrives, see Sending Delayed Revenue to Traffic Sources.

​
Troubleshooting

  • The campaign URL in 7SearchPPC is missing click_id={click_id}, or the macro was edited. Copy the URL from ClickFlare again.
  • REPLACE_WITH_ADVERTISER_ID was never replaced, or the Advertiser ID has a typo.
  • The postback uses 7SearchPPC’s CLICK_ID instead of ClickFlare’s {external_id}. ClickFlare doesn’t know CLICK_ID and sends it as literal text.
  • The offer never posted the conversion to ClickFlare. Check that the conversion shows in ClickFlare first.
  • Traffic source postback URL is off on the 7SearchPPC traffic source.
  • Disable sending postbacks to traffic source is on in the campaign.
  • The postback is mapped to a different event than the one the conversion logged. Check Logs → Event Logs to see which event was recorded.
  • Check Logs → Postback Status: a failed request shows the status code 7SearchPPC returned.
The template sends payout={payout}, so it was removed or edited. Restore &payout={payout} at the end of the postback.If the offer posts no payout to ClickFlare, {payout} is empty too. Check the conversion’s payout in ClickFlare first.
The macros were not replaced, usually because the URL was edited or pasted somewhere 7SearchPPC doesn’t process macros. Paste the campaign URL from ClickFlare unchanged into Destination URL. See Traffic Source Tokens Arriving Empty.
For the general checklist, see Conversions not showing.
FREQUENTLY ASKED QUESTIONS
Q1: Can I use the same 7SearchPPC traffic source for all my 7SearchPPC campaigns?
A1: Yes. The postback is set once on the traffic source and every campaign using it sends conversions the same way. Create a second 7SearchPPC traffic source only if you run a second 7SearchPPC account, since each account has its own Advertiser ID.
Q2: Why is it called click_id in the campaign URL and visitor_id in the postback?
A2: They are two halves of the same value. ClickFlare reads 7SearchPPC’s click ID from its own click_id parameter. 7SearchPPC expects it back in its own visitor_id parameter. Both names are fixed. Change neither.
Q3: 7SearchPPC’s guides mention Voluum, Binom and Keitaro, not ClickFlare. Is that a problem?
A3: No. 7SearchPPC’s postback works with any tracker that can fire a URL. The ClickFlare template already has the right URL. You only add your Advertiser ID.
Q4: Should I use Redirect or Direct tracking with 7SearchPPC?
A4: Redirect is the usual choice and works with every 7SearchPPC format. Use Direct only if 7SearchPPC must see your lander’s domain as the destination. See Direct Campaign Tracking.
Q5: Where do I see conversions on the 7SearchPPC side?
A5: Under Statistics in the left-side menu of your 7SearchPPC account. Compare them with ClickFlare’s numbers for the same campaign and dates.

Traffic source postbacks

Every token you can use in a postback.

Custom conversions

Pick the one event 7SearchPPC should count.

Cost models

How CPC, CPA and RevShare costs are calculated.

Conversions not showing

The general checklist when postbacks don’t arrive.