The Audiohook platform automatically tracks and identifies attributed events. Not only do we identify attributed events based on audio campaigns but we also identify events that are attributed to other channels such as Facebook and Google based on UTM parameters.

With that said, we understand that brands and marketers often have additional information relating to how events should be attributed such as post purchase surveys or historical customer data.

For these reasons, Audiohook support consuming additional attribution data in particular the channel the event should be attributed to. This can be done via GET or POST requests. The endpoint is shown below where {{account-specific-id}} should be replaced with your account uuid.{{account-specific-id}}/attribution

Note that your account uuid can be found by looking at your general Audiohook Pixel which should be implemented on each page of your website. Here is the structure of the Audiohook Pixel for reference.{{account-specific-id}}/pixel.png

For POST requests, data should be sent in as json in the body. At a minimum, the body should include event_name, event_id, and event_channel as these are required. Though any additional data can be included.

curl '{{account-specific-id}}/attribution' -H 'Content-Type: application/json' --data 'event_name={{EVENT-NAME}}&event_id={{EVENT-ID}}&event_channel={{EVENT-CHANNEL}}'

For GET requests, data should be sent as query string parameters. At a minimum, event_name, event_id, and event_channel should be included as these are required. Though any additional data can be included. Note that double curly brackets are to denote variables and should not be included.{{account-specific-id}}/attribution?event_name={{EVENT-NAME}}&event_id={{EVENT-ID}}&event_channel={{EVENT-CHANNEL}}
Did this answer your question?