Problem/Motivation

With Chrome's upcoming restriction on 3rd party cookies, we should have a way to use Tealium's option to get utag from a first party domain

Proposed resolution

Add a config option for 'first party domain url' and modify getUtagSyncUrl so that it can use it.

Issue fork tealiumiq-3418718

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

Brauny created an issue. See original summary.

brauny’s picture

StatusFileSize
new0 bytes
brauny’s picture

StatusFileSize
new1.18 KB
brauny’s picture

StatusFileSize
new2.62 KB
brauny’s picture

brauny’s picture

StatusFileSize
new2.95 KB
brauny’s picture

brauny’s picture

StatusFileSize
new3.15 KB
brauny’s picture

StatusFileSize
new5.73 KB
brauny’s picture

StatusFileSize
new5.73 KB
brauny’s picture

Status: Active » Needs review
brauny’s picture

StatusFileSize
new5.74 KB
jastraat’s picture

Do we want to make this an option or require the new 1st party domain field? Currently the patch makes it a required field. If it's a new required field, we might want to change the issue title...?

schiavone’s picture

Title: Add option to use 1st party domain for utag » Add required configuratiion to use 1st party domain for utag

I think we should make this required moving forward since optional opens ups issues with Chrome and possible future issues with other browsers. So I'm going to change the title and review the PR to see if we can get this merged.

schiavone’s picture

Title: Add required configuratiion to use 1st party domain for utag » Add required configuration to use 1st party domain for utag
schiavone’s picture

  • schiavone committed e530d8e1 on 8.x-1.x
    Issue #3418718: Add required configuration to use 1st party domain for...
schiavone’s picture

Status: Needs review » Fixed

The patch has been applied and merged into the 8.x-1.5 release. Thank you @Brauny for the patch and @jastraat for code review.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.