What if the subscriber already exists in my account?

What if the subscriber already exists in my account?

When a visitor submits information on your popup, we look for a matching email address and multiple phone records in order to complete the subscribe request. Shopify does not allow multiple customers with the same email address or phone number, so updates are made based on the existing email address and phones numbers.
  • Any customer, new or existing, that submits a popup will have the Seguno Popups tags added to the customer record.
  • A popup conversion is only recorded for new subscribers or when resubscribing a previously unsubscribed customer. A maximum of one conversion will be recorded per popup submission.
If you have specific concerns about if an email address and/or phone number already exist in your Customers, you may find specific use cases below.
  • If a popup with a form for email and SMS is submitted and Seguno does not find a matching record, we create one new customer subscribed to both email address and SMS.
  • If Seguno finds a matching record, we update the record to subscribed
  • If Seguno finds an email record but no phone number, and no other customer record with that phone number exists, we add phone and subscribe the customer for both email and SMS
  • If Seguno finds a phone number, but no email, and no other customer with that email, we add email to the customer and subscribe them to both
  • If Seguno finds the email addressed, but it has a different phone number than what was submitted in the form, we create a new record with the phone and subscribe, then subscribe on the current email record - we note on the new record there could be a duplicate, tag with seguno-duplicate
  • If Seguno finds two existing separate customer records for email and phone, we subscribe both separately
  • If the popup contains forms for phone and email on different steps, Seguno submits the email address first and creates or updates the customer appropriately.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.