Understanding HTTP(S) Requests
A standard HTTP(S) request used for tracking looks like this:- http(s): The communication protocol used (secure HTTPS or standard HTTP).
- platform_domain.com: The destination domain where the request is sent. In ClickFlare, this could be your campaign tracking domain.
- directory: An optional path that directs the request to a specific resource.
- parameter1, parameter2, etc.: Parameters recognized by the receiving platform, used to pass tracking data.
- {token}: A placeholder that dynamically changes based on user interactions, such as click ID, country, or device type.
Key Information Transfers in ClickFlare
Data is passed through different stages in tracking, forming a complete loop:- From Traffic Source to ClickFlare: Click data (e.g., click ID, ad ID, placement ID) is passed via tracking links.
- From ClickFlare to the Affiliate Network: ClickFlare forwards relevant data (e.g., click ID, sub-IDs) to the affiliate network using the offer URL.
- From Affiliate Network Back to ClickFlare: The affiliate network notifies ClickFlare about conversions using a postback URL.
- From ClickFlare to the Traffic Source: ClickFlare reports conversion events to the traffic source via postback or conversion API.
Q1: What happens if a tracking parameter is missing in the request?A1: If a required parameter is missing, the receiving system may not correctly attribute clicks or conversions, potentially affecting campaign tracking.
Q2: Can I customize the tracking parameters in ClickFlare?A2: Yes, ClickFlare allows you to define custom parameters and tokens to ensure compatibility with your traffic sources and affiliate networks.
Q3: How does ClickFlare handle secure data transmission?A3: ClickFlare supports HTTPS to ensure encrypted and secure data transfer between platforms.