AI-generated Key Takeaways
-
A call conversion includes fields such as custom variables, consent settings, caller ID, and the start time and date of the call.
-
Key information for a call conversion includes the associated conversion action, the date and time the conversion occurred, the conversion value, and the currency code.
-
The caller ID should be in E.164 format with a preceding '+' sign, and the call start and conversion date/time fields require a specified timezone in a specific format.
A call conversion.
Fields | |
---|---|
|
The custom variables associated with this conversion. |
|
The consent setting for the event. |
|
The caller id from which this call was placed. Caller id is expected to be in E.164 format with preceding '+' sign, for example, "+16502531234". |
|
The date time at which the call occurred. The timezone must be specified. The format is "yyyy-mm-dd hh:mm:ss+|-hh:mm", for example, "2019-01-01 12:32:45-08:00". |
|
Resource name of the conversion action associated with this conversion. Note: Although this resource name consists of a customer id and a conversion action id, validation will ignore the customer id and use the conversion action id as the sole identifier of the conversion action. |
|
The date time at which the conversion occurred. Must be after the call time. The timezone must be specified. The format is "yyyy-mm-dd hh:mm:ss+|-hh:mm", for example, "2019-01-01 12:32:45-08:00". |
|
The value of the conversion for the advertiser. |
|
Currency associated with the conversion value. This is the ISO 4217 3-character currency code. For example: USD, EUR. |