AI-generated Key Takeaways
-
A call conversion can include custom variables and consent settings.
-
Key information for a call conversion includes caller ID in E.164 format, call start date and time with timezone, conversion action resource name, conversion date and time after the call time with timezone, conversion value, and currency code in ISO 4217 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. |