Skip to content

Newsletter signup requests pass location (country) and location state#28681

Open
rBangay wants to merge 7 commits intomainfrom
rb/newsletter-signup-geolocation
Open

Newsletter signup requests pass location (country) and location state#28681
rBangay wants to merge 7 commits intomainfrom
rb/newsletter-signup-geolocation

Conversation

@rBangay
Copy link
Contributor

@rBangay rBangay commented Mar 24, 2026

What is the value of this and can you measure success?

The CRM teams for the different regions cannot personalise marketing based on region for users without a registration_location set.

Currently the US has a workaround in which these ‘regionless’ users are counted as US users if they have signed up for a US editorial newsletter but this could result in false positives and a poor CRM experience.

What does this change?

Pass location and location state (If in US or AUS) through to the /consent-signup and /consent-email IDAPI endpoints when a user signs up for a newsletter

Richard Bangay added 2 commits March 24, 2026 10:41
@rBangay rBangay added the feature Departmental tracking: work on a new feature label Mar 24, 2026
Richard Bangay added 2 commits March 25, 2026 22:30
…on to get rid of duplication. Make the way we get the country code more readable
@github-actions
Copy link
Contributor

github-actions bot commented Mar 25, 2026

@rBangay rBangay marked this pull request as ready for review March 25, 2026 22:46
@rBangay rBangay requested a review from a team as a code owner March 25, 2026 22:46
Comment on lines +97 to +100
"privateFields" -> (
"registrationLocation" -> registrationLocation,
"registrationLocationState" -> registrationLocationState,
),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"privateFields" -> (
"registrationLocation" -> registrationLocation,
"registrationLocationState" -> registrationLocationState,
),
"registration-location" -> registrationLocation,
"registration-location-state" -> registrationLocationState,

I suggested privateFields because I thought this was going to be using the /guest endpoint, but I think we'll implement it slightly different for the newsletter signup endpoints!

…ove privateFields request body property/object
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Do not merge ⚠️ feature Departmental tracking: work on a new feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Send geolocation in POST request to IDAPI newsletter signups from frontend

3 participants