Updating User Email in Segment Creates new User in Customer.io

Question

Hi there -

I use Segment to pipe my data in to c.io. When I call identify, if a user’s email has changed, it is a normal identify call, and I expect c.io to just update the email address of the user. This is what’s happening in mixpanel, for instance. But in c.io I noticed that it’s actually creating a new user, and it is not setting ID (my app’s ID), because a user already exists with that ID.

Is there some way I need to tweak these identify calls to accomodate this?

icon

Best answer by Penny 18 August 2023, 09:06

View original

Penny · Accepted Answer

Hey @jakesingThe solution to this might depend on whether your workspace uses both id and email as an identifier (or only id) and whether your workspace settings allow the email attribute to be updated via both cio_id or id:It sounds like your workspace settings currently is only allowing the email identifier to be updated by cio_id, which is why when you call identify to change the email, it is creating a new profile instead.Once you’ve updated this setting in your Workspace Settings > General Workspace Settings, this should work as expected. ◡̈I’ve also linked our help documentation on this for Segment Destinations Actions for your easy reference and this would go more into detail:https://customer.io/docs/journeys/segment-destination/#cio_id-update.Hopefully this helps!

jakesing · Answer

Hi Penny - thanks a lot! I actually did see this before I posted, and I do Ihave that setting checked (per your screenshot). Could anything else be going on?

Updating User Email in Segment Creates new User in Customer.io

3 replies

Reply

Reply

Sign up

Login to the community

Scanning file for viruses.

This file cannot be downloaded