| Tracking and Conversions | |
Profiler is responsible for parsing the Conversion log entries and updating the database tables as well as populating the Conversion_History. Profiler updates the tables differently depending on the information passed in the Conversion log entry.
Link Context (best case)
If the full link context is provided, then all IDs are updated in the Conversion History table and all Profiler tables can be updated.
If multiple link contexts are provided and the conversation name is also provided in the detector data, use the link context for the conversation.
If multiple link contexts are provided and instance IDs are different, use the one with highest instance ID.
Customer_ID
If the kc_customer cookie is available, but not the kc_click cookie, then only a subset of the Profiler tables can be updated.
The conversion is external, meaning it is not associated with a Connect campaign. This can happen if the conversation name does not match any of the link cookies by instance ID.
CustomerID in Detector Data
If no cookie data is available, but the customerID is provided through the conversion detector, Profiler attempts to identify the customer and continue as described in the Customer_ID only section above. Clients can use this approach if they don’t want to use cookies but they have data for customerID.
If no cookie data exists and the customerID is invalid, try using the information in the Email Address section.
Email Address
If no cookie data is available and there is no customerID in the conversion detector data, but the e-mail address is provided through the conversion detector, then Profiler attempt's to identify the customer and continue as described in the Customer_ID section above. Clients can use this approach if they do not want to use cookies.
If Connect cannot identify a valid customer ID at this stage, the log entry is discarded.
If no cookies are available and no data is provided by the conversion detector, then the conversion log entry is discarded. This can only happen when the customerID or e-mail address provided in the conversion detector is not in the database. Tracker has no access to the database.
Interests and Conversion Value
If the conversion detector provides a total then it is recorded. If interests and subtotals are provided, they are recorded as well.
If no total is provided, the conversion value from the associated link is used instead.
If interests are provided, they are used to populate Conversion_Interests. Otherwise, interests from the associated link is used.
If subtotals and interests are provided, they are also used to populate Conversion_Interests. Otherwise, interests from the associated link is used and the entire total is accredited to each of them.
If the invoice number is provided, the conversion history table is queried for a match. If present, the current conversion is considered a duplicate and is discarded.