Profile vs Subscription

Noticia models two distinct things. Keeping them separate is the key to staying compliant while still marketing effectively.

Profile

A profile is a customer identity, mirrored from your CRM. It is addressed by external_id, your own stable identifier for that customer. A profile can carry a phone number, a name, and attributes, but holding a phone number does not mean you are allowed to text that person.

POST /v1/profiles is an upsert keyed on external_id: calling it twice with the same id updates the profile instead of creating a duplicate. Your CRM stays the source of truth; Noticia layers activation on top.

Subscription

A subscription is SMS marketing consent for a single phone number. It records:

• status: SUBSCRIBED or UNSUBSCRIBED.
• consent_source: where the consent came from (WEB_FORM, IN_STORE_TABLET, LOYALTY_PROGRAM, and so on).
• consented_at: when consent was given.
• consent_proof: the evidence you keep for a GDPR/CNIL audit.

Noticia only ever sends marketing SMS to a phone number that has a SUBSCRIBED subscription. A STOP reply, an opt-out call, or an action in the app flips the status to UNSUBSCRIBED immediately.

The phone number on a profile is not consent

A Profile.phone_number is an identity field. The phone number Noticia texts is the one on the subscription. Storing a number on a profile never makes that person reachable by SMS. Consent is always explicit, through a subscription.

How they connect

A subscription references a profile with profile_id (your external_id or the prefixed prof_ id) so the same person ties together across your data. A profile can exist with no subscription (you know the customer but have no SMS consent), and an opt-in can auto-create a profile if the customer is new.

	Profile	Subscription
Represents	Customer identity	SMS marketing consent
Addressed by	external_id or prof_...	phone number (+ profile)
Lets you send SMS	No	Yes, when SUBSCRIBED
Source of truth	Your CRM	The consent moment

Next: capture consent the right way.