When a call is made to a Delacon tracking number, the callers phone number (Caller ID) is captured and displayed in the Delacon call reports (unless the caller has chosen to hide or restrict their number). Delacon can then pass this number into Google Analytics, however due to restrictions on Personally Identifiable Information (PII) the caller number must first be hashed (using SHA-256) before it is sent. This ensures that the caller cannot be identified from the data in GA alone, but using the phone number in the Delacon call log a hash can be created and searched for to find all calls from that same caller within GA.
The caller phone number is sent under the following variables, depending on the version of GA being used:
Google Analytics 4 (GA4)
-Sent as a custom dimension when using the calltracking_IncomingCallNumber parameter, and can be seen in Event reporting:
Please see step three of our Google Analytics 4 Integration guide for setup instructions.
Google Analytics 3 (Universal Analytics)
-Sent as a custom dimension and can be seen when applying the Caller secondary dimension to the Delacon call events (calltracking/repeat/offline)
Please see steps two and three of our Universal Analytics Integration guide for setup instructions.
To find the details for a particular caller in GA, you will first need to know the callers phone number and then hash the number in the E.164 international format (country code + area code + number). Please note that the "+" sign should not be included. The hashed value can be generated through a SHA-256 hash generator.
Caller number: Australian mobile 0412345678
Converted to E.164: 61412345678
Hashed value: 222e24d90b23ba2af558a2891bfa399f19a7eb9f33df34a7d6809b97c5a97246
Please sign in to leave a comment.