Skip to main content

Minor Personas

Minors appear in contact lookups but are restricted: no messaging, loyalty, exports, or audience inclusion. Identified via isMinor with limited profile data.

Updated over 3 weeks ago

Minors appear in the contact list endpoint (GET /piis/:uid) and full contact lookups by their contactID or srcID. Minors are not added to cache. Any operation that relies on a contact existing in cache will fail for minors, including:

  • Opt-ins (SMS, email, push, browser)

  • Campaign targeting and messaging

  • Audience inclusion

  • Loyalty point assignment

  • Exports and syncs

Minors are identified by a customAttribute with key: "isMinor" and value: "true". Additional custom attributes include guardianContactID, guardianName, and customerType: "minor"

While they may appear as though they are returned with the other contacts they are not, more importantly a minor's signed up date is when the form was submitted. Normally this would be an opt in date, or loyalty date. Since minor contacts will not be able to ever have either those options weren’t available to us, so we added something to allow them to be sorted.

What minors can do:

  • Appear in the contact list alongside regular contacts

  • Be searched by name

  • Be viewed via full contact lookup (contactID or srcID)

  • Display a minimal profile with name, DOB, guardian info, and customer type

  • Be created through signup form submissions with waiver data

What minors cannot do:

  • Receive any marketing messages (SMS, email, push, etc.)

  • Be opted into any communication channel

  • Be added to audiences or segments

  • Earn or redeem loyalty points

  • Appear in exports or syncs

  • Have purchase history, actions, or conversion data

  • Merge with another profile

Minors cannot merge with or be unmerged to any other contact, and we will show a minified view when someone tries to look up a minor contact, note this is the mockup but gives the general idea.

Did this answer your question?