Introduction
The 24metrics JavaScript Integration Wizard enables seamless screening of affiliate traffic directly on your landing pages. The JavaScript integration offers a streamlined solution for real-time fraud detection across impressions, clicks, and conversions.
By embedding JavaScript tags into your landing page or conversion page (Thank You page), you can swiftly implement fraud prevention filters and protect your campaign budget in no time.
This integration enables immediate identification and blocking of fraudulent activities such as bots, VPNs, and ad stacking, ensuring that only legitimate traffic reaches your campaigns. With customizable filters 24metrics provides a flexible and efficient approach to safeguarding your digital advertising efforts.
1. Javascript Integration
- From your Dashboard, go to Integrations menu end click +Create
- Name the integration (can be changed later) and select the Javascript option then click Save & Proceed To Setup
2. General Settings
Define the blocking strategy:
- Redirect to Fallback URL: insert a custom URL where the rejected clicks should be redireted
- Show Blank Page: when a click is flagged as fraud, the user will see a blank page
Additional Options:
- Active: turn the integration On and Off. When turned Off, no clicks or conversions will be screened
- Enable IP Provacy: when enabled, the IP adresse will be obfuscated in reports and exports
- Use Current Time: if disabled, the server time UTC will be used for clicks and/or conversions.
3. Code Generator for Clicks
Clicks Script:
- Define the additional parameters
- Copy the script
- Embed is on the landing page in the <Body> html section
How parmaters are used:
- If Google Tag Manager is used, utm_ parameters are going to be mapped automatically.
- All the other parameters of the current page are passed to our system. Non-standard parameters will be saved as Extra Parameters in the report.
Custom Coding Requirement:
- If you need to dynamically change the parameters such as: Offer, Advertiser, Publisher, and Sub IDs, you are required to add the replacement logic for the {TOKENS} in the code.
How Fraud detection will work:
- Show Blank Page - if this is chosen method, the code will show a blank page to the user.
- Fallback URL - if this is the chosen method, the code will redirect the user to the defined url.
- Monitoring Mode - If monitoring mode is on, no blocking or redirecting will happen regardless of the blocking method that is chosen. The click will still be marked as rejected in the Reports.
4. Code Generator for Conversions
Conversion Script with Click Lookup
The script is designed for use when both click and conversion events are configured for fraud screening. It supports conversion validation through click-level lookup, where the system uses the provided transaction_id to search for a matching click. Please note that this process is not real-time - the conversion is only recorded after the click match is verified.
How Parameters are passed to our system?
- With Click Lookup feature, we will automatically find the click that is stored in our system and create a new Conversion from it.
- Custom coding is required to dynamically replace additional parameters such as Revenue, Payout, and Purchase Value.
- Non-standard parameters will be saved as Extra Parameters in the report.
Conversion Script for Clickless Conversions
The code generater for clickless conversion screening will provide a JavaScript code that enables real-time validation and screening. Unlike traditional click lookup methods that rely on stored click data, this approach processes incoming data on the fly and provides instant responses.
To maximize detection accuracy and ensure reliable conversion attribution, it's strongly recommended to include as much contextual information as possible in your code snippet. Key parameters include Offer, Publisher, SubID, Payout, Revenue, Referrer URL, etc.
Any additional metadata relevant to the conversions. This allows our system to perform intelligent, real-time analysis of each conversion event - improving fraud detection, attribution precision, and overall tracking integrity.
Custom Coding Requirement
- You are required to add the replacement logic for the {TOKENS} in the code to dynamically pass the tracking parameters.
- You must pass the standard tracking parameters: Offer, Advertiser, Publisher, and Sub IDs.
How to pass Parameters to track Conversion?
- Custom coding is required to dynamically replace additional parameters such as Revenue, Payout, and Purchase Value.
- Non-standard parameters will be saved as Extra Parameters in the report.
5. Labels
Labels allow users to assign custom, human-readable names to offer or publisher IDs, making reports easier to read and analyze. Instead of displaying raw IDs, the system will show the assigned labels wherever those IDs appear in reporting.
Labels can be applied individually to specific offers or publishers to enhance clarity and streamline workflow.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article