Redirect URL integration

Set up a Redirect URL integration so 24metrics can screen clicks before they reach your offer. Use this with platforms such as Everflow, HasOffers, Trackier, Affise, Cake, or Swaarm, or with a custom tracking setup.

How it works

A Redirect URL integration puts 24metrics between your tracking link and the offer:

1. An affiliate clicks your tracking link.
2. The tracking link points to a 24metrics protected link.
3. 24metrics screens the click for fraud.
4. If the click is clean, 24metrics redirects to the original offer URL.
5. If the click is rejected, 24metrics blocks it or sends it to a fallback URL.

What you will do

Step	Action
Create the integration	Go to Integrations → Create → choose Redirect URL → Next
Choose a template	Set Tracking Platform Links Template to your platform, or Custom
Map macros	Required only when the template is Custom
Create a link	Paste the offer landing page URL into 24metrics and save
Update your platform	Replace the offer URL with the protected link from 24metrics
Enable filters	Open the Global Filters tab and turn on the checks you need
Choose fraud action	Block rejected clicks, or send them to a fallback URL

Integration setup

Create a redirect URL integration

1. Open Integrations in the main menu.
2. Click Create.
3. Enter an Integration Name (for example, Everflow or Demo Lead Gen).
4. Under Select Integration Type, choose Redirect URL.
5. Click Next.

Choose a tracking platform template

On the next screen, set Tracking Platform Links Template:

• Choose your platform when it is listed: Everflow, HasOffers, Affise, Trackier, Cake, or Swaarm.
• Choose Custom if your platform is not listed or you use a proprietary tracker.

You can change the template later. If the integration already has many links, create a new integration instead of changing the template on the existing one.

Custom parameter mapping

If you chose Custom, map the macros your platform uses so 24metrics can pass the right values through the protected link.

Example mapping:

• Publisher Macro → {affid}
• External Transaction ID → {clickid}
• Sub ID Macro → {sub1}
• Device ID → {device_id}

Use the exact tokens your platform expects.

When the mapping looks correct, click Save.

Platform templates

If you chose a supported platform template, parameter mapping is preconfigured. You do not need to map macros yourself.

Platform-specific setup notes:

• Everflow, HasOffers, Affise, Trackier, Cake, and Swaarm redirect setup

Wait for the integration to be ready

After you save, wait up to 20 minutes before you use the integration. Check the readiness status on the integration page. When it shows ready, continue with the link steps below.

Create a protected link for your offer

Overview

Create one Link for each offer or landing page you want to protect. Saving the link generates a protected URL that you paste back into your tracking platform.

Prerequisite

In your tracking platform, open the offer URL configuration and copy the destination URL, including any parameter macros.

Create the link

1. Open the integration and go to the Links tab.

2. Click Create.

3. Enter a Link Name. Use the same name as the offer when you can.

4. Paste the destination URL into Enter Landing Page URL, exactly as it appears in your platform.

5. Optional: turn on Send Rejected Clicks to a Fallback URL? and enter a fallback URL. By default, rejected clicks see a blank page.

6. Click Save.

   

7. Copy the generated protected link.

8. In your tracking platform, replace the original offer URL with the protected link.

Testing the integration

1. From your platform, generate a normal click tracking link for the offer.
2. Open that tracking link in a browser.
3. If you see a blank page, or you land on the fallback URL, the click was rejected and screening is working.
4. Open Reports → click reports and confirm a new click appears after a few seconds.

Known issues

• Connection is not secured.
• This site can’t be reached.

If you see either message while testing, wait the full 20 minutes after creating the integration. If it still fails, contact support.

Configuring fraud protection

Open the integration Global Filters tab. Choose Clicks, Conversions, or Impressions, then enable the checks that apply to this traffic. Common click checks include Emulator & Bots, VPN / Proxy, Click Flooding, GEO Filter, Device Anomaly, and Compliance Checks.

Global filters are the fallback when no custom group matches. Use Filter Groups for source-specific rules and separate click and conversion preset browsing.

Example: enable bot protection

1. Open the Global Filters tab.
2. Select Clicks.
3. Open Emulator & Bots and enable Enable Emulator & Bots Filter.
4. Configure the visible options, select Done, then use the page-level Save changes action.

Blocking vs monitoring mode

Under Click Fraud Screening Options (Prevention / Detection), choose the blocking or monitoring mode and select Save changes. Preset browsing and filter drawers use the same editor as Filter Groups.

Monitoring mode

Rejected clicks still appear in reports, but they are not blocked or redirected. Use this when you want to measure fraud before you enforce blocks.

Blocking mode (default)

Rejected clicks are blocked or sent to the fallback URL you configured on the link.

Common mistakes to avoid

• Do not manually change parameter tokens in the offer URL after mapping is set.
• Do not skip macro mapping when the template is Custom.
• Do not leave filters disabled if you expect fraud screening to protect the offer.

Next steps

• Platform redirect URLs for Everflow, HasOffers, Affise, Trackier, Cake, and Swaarm notes
• Click reports to verify screened traffic
• Affiliate postback setup when you need conversion callbacks