Skip to main content

Use Case: Prompt to join the community

Engagement: Multi-question survey (you’ll see why below, perhaps there’s a better approach?)

Step 1 is a single question with two options: 

  1. Take me to the community
  2. I already have a community account

Conditional Logic desired based on response: 

  1. Take me to the community -- end survey (and will set logic to open community in new tab)
  2. I already have a community account -- proceed to step 2 (with open text question to collect their email address) 

Objectives: 

  • Drive community sign ups and adoption for new users
  • Collect associated email addresses for existing users who already have accounts
    • We have some users (ex. our partners) who user our product via multiple emails and logins
    • When identified, we will update our records so that their user attributes reflect that they have an account

 

I’m using a survey because I need to collect the email addresses when option 2 is selected, but is there a better way? 

I ask this question because the conditional branching logic seems to be forcing me to route response 1 to an additional step. 

I agree that the multi-question survey is the best available approach for any PX engagement that requires text input from the users. Any other approach would require custom JavaScript-enabled html form(s) in the engagement design. Easy enough, but in a best-case scenario, your application’s security settings probably won’t allow that approach (and rightly so).

Thanks for your help, ​@rschlette.

I ran into a blocker. I can’t set an action on the submit button of a multi-step survey like I can for other engagements. 😟

So for primary path, there’s no way for the survey to open the community in a new tab. 

Would it be possible to do this via two separate engagements? 

Engagement A is a guide or dialogue with two button options. 

  1. Create account - closes engagement, opens community in a new tab
  2. I already have an account - triggers engagement B 

Engagement B is a single question text input survey that ignores throttling and I figure out some audience logic to get it to show immediately?  

That would work, yes. I’d use a v2 Guide engagement for Engagement A, so the dialog’s custom buttons can make use of the server-side actions. Both could be redirects: one to the community page in question and the other to $px-auto-resolve?form=true or similar. Then your audience logic for Engagement B could require the query param of your choice, i.e. whatever is in the engagement A, button 2 redirect

​@rschlette incredible! thanks for your help? 

Is it possible to redirect to the current page and add a query param to trigger the second one? How would I put that into the url? 

Yes, you can add a single PX Auto Resolve token, then the param and value. So if you wanted to stay in the same path, but add the param ‘form’, the redirect value would be:

$px-auto-resolve?form=true

 

That will do the trick

Terms & ConditionsCookie settingsAccessibility statement