When a customer clicks a link in a Connect message, two cookies are set in the customer’s
browser: kc_customer and kc_click.
- kc_customer is the customer_id and has a long expiration date
(sysparam).
- kc_click contains the full click context (customer_id, instance_id,
event_queue_id, and link_id). This cookie has an expiration (1-2 days -
sysparam). The cookie name includes the instance ID (kc_click_127). As a result,
there is one cookie for the last click of each link instance.
- HTML and Read detectors These pseudo-clicks only set the kc_customer
cookies.
When Tracker recognizes a click-through as a conversion, it bypasses the normal
click-through handling code. It creates a ConversionLogEntry (logger package) containing
the click-through context retrieved from the cookie and the unparsed query string from
the conversion detector.
If Tracker receives multiple link cookies they are stored in the log entry. Profiler
selects the appropriate cookie.
Duplicates
After receiving a conversion, Tracker sets a third cookie, kc_confirm (with a short
timeout sysparam). If this cookie is present when the conversion is received,
Tracker assumes the conversion is a duplicate and discards it. The value for this
cookie is the date the last conversion was received.
System Parameters
Tracker uses the following parameters:
- Use cookies: yes/no - If no, Tracker will never set cookies.
- Timeouts: - Each of the three cookies have a timeout parameter.
- kc_customer - Extended timeout parameter.
- kc_click - Timeout parameter of 1 to 2 days.
- kc_confirm 30 minute timeout parameter.
- No cookies are included. Cookies can be blocked, expired or never set
(sysparam). If the conversion detector data includes the e-mail address,
then a log entry is created. Otherwise, the conversion is discarded.
- If some cookies are present but not others, the log entry contains the data
present.
- If kc_confirm is present the conversion is discarded as a duplicate.
See Profiler for additional rules.