Messaging

The following images matches what we can see on any bleep stores at the moment.

Initial view

Screenshot_2019-08-20_at_12.09.08.png

Cookie preferences expanded

Screenshot_2019-08-20_at_12.09.01.png

The cookie message is loaded based a cookie message object and the opt out options are dynamically loaded based on the cookie preference included in that same object.

Object

The cookie message object with the correspondent preferences can be loaded from the matching store domain as JSON:

https://bleep.com/analytics/cookies

Properties

Screenshot_2019-08-20_at_11.58.29.png
preference.items[].param 

is a GET parameter that needs to be linked with opt out checkboxes shown on the previous section.

Acceptance

Hitting Accept Cookies or Accept Selected Cookies needs to trigger the post-back to write the actual cookie params that will then be verified on the next refresh. These params will be also used by the backend to request the correspondent tracking snippets (matching the selected preferences)

While integrating with third-party websites an extra call is required to make sure the acceptance is considered for the supporting store too.

https://bleep.com/register/acceptCookies

The “a” and/or “ma” GET params need to be added:

?a=true&ma=true

Snippets

Similarly to what was described before to load the tracking snippets we need to specify the preferences that were chosen by the client.

https://bleep.com/analytics/snippets

GET “a” and/or “ma” params.

?a=true&ma=true
Screenshot_2019-08-20_at_11.57.35.png

These call needs to be done on the backend considering that the results snippets need to be loaded on the very first stage of the page load, inside the head tag.

Did this answer your question?