Consent Timeline - Consent Events

In the Consent timeline tab of the Profile view you can see a comprehensive timeline of a Profile's channel consent (opt-in, confirmed opt-in and opt-out) in relation to your APSIS One activities.

Individuals can provide and withdraw different types of consent, in various levels.

Profiles' consent can be generally divided in two different statuses, and this is often enough to understand whether a Profile will or will not receive your communications:

  • Opt-in: Subscribed, provided consent.

  • Opt-out: Unsubscribed, withdrawn consent.

However, there are different types of consent, and this is most relevant to you when enabling Double Opt-in!

For a deeper look into the types of consent, head over here.

consentTimeline2.jpg


In this article


Website Tool: Sign-up Bar Consent

Sign-up Bar: Email Consent

They provided their email consent (opt-in) via a Sign-up bar. The Sign-up bar - Submit Event is logged into Unknown Profiles who enter their email into your Sign-up bar, and a Known Profile is then created with an Email Consent Event. Browsing data prior to the consent is kept in the Unknown Profile with the Submit Event, until the Known and Unknown merge due to additional browsing behavior or Double Opt-in. When merged, both Events will be present in the merged Profile.

Here are the types of data associated with this Event:

activityId: The ID for the particular Sign-up bar activity that is considered the source of the Event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

referrer: The page where the website traffic originated, or where the Profiles were before reaching the domain where the Sign-up bar was placed.

url: The URL where the visitor filled in the Sign-up bar.

domain: The domain where the Sign-up bar was placed.

location: The country where the Event happened, in the ISO 3166-1 alpha-2 format (SE, US, for example).

address: The Email the person associated with the Profile provided with their explicit consent.

topicIds: The ID for the Topics that the Profile subscribed to.

targetId: The ID for the Consent list that is associated with the Event.

referrer: The page where the website traffic originated, or where the Profiles were before reaching the domain where the Sign-up bar was placed.

url: The URL where the visitor filled in the Sign-up bar.

domain: The domain where the Sign-up bar was placed.


Sign-up Bar: SMS Consent

They provided their SMS consent (opt-in) via a Sign-up bar. The Sign-up bar - Submit Event is logged into Unknown Profiles who enter their mobile number into your Sign-up bar, and a Known Profile is then created with an SMS Consent Event.

Browsing data prior to the consent is kept in the Unknown Profile with the Submit Event, until the Known and Unknown merge due to additional browsing behavior or Double Opt-in. When merged, both Events will be present in the merged Profile.

Here are the types of data associated with this Event:

address: The mobile number the person associated with the Profile provided with their explicit consent.

source: The ID for the particular Sign-up bar activity that is considered the source of the Event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

location: The country where the Event happened, in the ISO 3166-1 alpha-2 format (SE, US, for example).

topicIds: The ID for the Topics that the Profile subscribed to.

targetId: The ID for the Consent list that is associated with the Event.


APSIS Pro: Email Consent

This Event happens when a visitor submits their consent to email communications related to APSIS Pro. The Migration Wizard creates or updates an APSIS One Profile with Topic consent in your APSIS One account. This Event will only be created in APSIS One Profile if you have an active migration.

Here are the types of data associated with this Event:

mailinglist: The unique ID of the APSIS Pro mailing list.

address: The email address of the person associated with the Profile provided with their explicit consent.

targetId: The ID for the Consent list that is associated with the Event.

topicId: The ID for the Topic that the Profile subscribed to.


Forms & Pages tool: Forms Consent

Forms: Email Consent

They provided their email consent (opt-in) via a Form. The Forms - Submit Event is logged into Unknown Profiles who complete your Form, and a Known Profile is then created with an Email Consent Event. Browsing data prior to the consent is kept in the Unknown Profile with the Submit Event, until the Known and Unknown merge due to additional browsing behaviour or Double Opt-in. When merged, both Events will be present in the merged Profile.

address: The mobile number the person associated with the Profile provided with their explicit consent.

activityId: The ID for the particular Forms activity that is considered the source of the Event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

location: The country where the Event happened, in the ISO 3166-1 alpha-2 format (SE, US, for example).

topicIds: The ID for the Topics that the Profile subscribed to.

targetId: The ID for the Consent list that is associated with the Event.

referrer: The page where the website traffic originated, or where the Profiles were before reaching the domain where the Form was placed.

url: The URL where the visitor filled in the Form.

domain: The domain where the Form was placed.

Forms: SMS Consent

They provided their SMS consent (opt-in) via a Form. The Forms - Submit Event is logged into Unknown Profiles who enter their mobile number into your Form, and a Known Profile is then created with an SMS Consent Event. Browsing data prior to the consent is kept in the Unknown Profile with the Submit Event, until the Known and Unknown merge due to additional browsing behaviour or Double Opt-in. When merged, both Events will be present in the merged Profile.

address: The mobile number the person associated with the Profile provided with their explicit consent.

source: The ID for the particular Form activity that is considered the source of the Event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

location: The country where the Event happened, in the ISO 3166-1 alpha-2 format (SE, US, for example).

topicIds: The ID for the Topics that the Profile subscribed to.

targetId: The ID for the Consent list that is associated with the Event.

referrer: The page where the website traffic originated, or where the Profiles were before reaching the domain where the Form was placed.

url: The URL where the visitor filled in the Form.

domain: The domain where the Form was placed.


Email - Confirmed double opt-in

An Event added to the Profile when they confirm a sign-up from a form with double opt-in enabled.

topicIds: The ID for the Topics that the Profile subscribed to.

targetId: The ID for the Consent list that is associated with the Event.


Sleeknote Consent

Read more about Sleeknote Profile data in this article.

Did this answer your question?