Skip to main content

Hi
Is it possible to have to import a CSV to define the audience of an engagement? Or a workaround for this?

Use case: The users in PX are created the first time they log into our platform, and we have several FTUs engagements for them. 
We need to target them with an engagement with a Dialogue but one Engagement should exclude some users based on some attributes. As such, we can’t define the “is not” part of the audience within the platform because the users do not exist in PX, but we can source them from Salesforce.
 
Currently we are exporting the report to a sheet file with a Fx to concatenate the addresses, copy paste from that concatenated cell and define the audience that way. Also, this is limited to x1000 emails, so when that threshold is surpassed, a new step in the audience is needed.
 


We have in the roadmap different FTU engagements according to roles and other criteria, so maintain daily 10x engagements this way is unsustainable.

Is there a better way to achieve this use case?
Thank you,

Hi @romihache 

I am not sure if this would help as the users are not yet in PX, but you might want to look at the Segment functionality to determine if you could capture the individuals/accounts into a segment as they are authenticating the first time into your product.  But I think that we might have the same issue that we cannot do an “exclude the segment” for your engagements.

 

So if we took the above theory and reversed it - is it possible to create a segment for everyone that should be included on authorization and use that segment as a match requirement in the other engagements?

 

 

Might want to upvote this feature also… incase we get exclusion functionality in the future.

 

You might want to move this Question to Features to get upvotes.

Thank you @lpicone !
Yeap, I wanted to be sure there is no other way around it before submitting the idea. Thank you very much for taking the time to reply!

Not PX, but I know @ssamarth is planning something with Segmenting in Surveys :) 

Reply


Terms & ConditionsCookie settings