Skip to main content

Newsletter Subscribed

When to Use

Trigger this event when a visitor subscribes to a newsletter, mailing list, or email updates — through a dedicated form, a popup, a footer opt-in, or any other subscription mechanism.

This event is separate from lead_created because newsletter subscriptions typically represent a lower level of intent. Use lead_created for contact forms, demo requests, and other high-intent actions.

Complete Reference

event object required

name string required

info

Use only static value newsletter_subscribed for event.name.

name: "newsletter_subscribed"

value number

info

Estimated value of the subscription. Optional — set to 0 if not applicable.

value: 0

currency string

info

Currency code. Falls back to the default currency from your configuration.

currency: "EUR"

context object

url string required-if-applicable

info

Collected automatically for standard websites. Required only for SPA applications where URL changes don't trigger automatic page context updates.

url:"https://shop.example.com/products/laptop?color=silver&storage=512gb&utm_source=google"
warning

URL Parameter Sensitivity: Be mindful of sensitive information in URLs. Query parameters may contain personal identifiers, session tokens, or private information that should be handled according to privacy regulations.

page_type string recommended

info

Type of page (product, home ...)

page_type: "product"

environment string recommended

info

Allowed values: prod, dev

environment: "prod"

user object required

info

The user object must include at least an email address for newsletter subscriptions.

View complete User Object documentation

id string recommended

info

Unique customer identifier in your system.

id: "CUSTOMER_INTERNAL_ID"

email string recommended

info

Customer email address in plaintext. Do not send pre-hashed values — DATA Reshape automatically normalizes and hashes before sending to destinations.

phone string recommended

info

Customer phone number in E.164 format (plaintext). Do not send pre-hashed values — DATA Reshape automatically normalizes and hashes before sending to destinations.

phone: "+40712345678"

first_name string recommended

info

Customer first name

first_name: "John"

last_name string recommended

info

Customer last name

last_name: "Doe"

country string

info

Country name or ISO country code

country: "Romania"

region string recommended

info

State, province, or region name

region: "Bucuresti"

city string recommended

info

City or locality name

city: "Bucuresti"

street string

info

Street address including number

street: "Strada Principala 1"

postal_code string

info

Postal code or ZIP code

postal_code: "700000"

orders_total_number number recommended

info

Cumulative number of orders placed by this user

orders_total_number: 5

orders_canceled_number number recommended

info

Cumulative number of orders placed and canceled by this user

orders_canceled_number: 0

orders_total_value number recommended

info

Cumulative lifetime user orders value (decimal format: 2500.50)

orders_total_value: 1234.99

orders_refunded_value number recommended

info

Cumulative lifetime user orders value canceled (decimal format: 2500.50)

orders_refunded_value: 250.99

predicted_value number

info

Predicted lifetime value of a customer for your business

predicted_value: 100.99

created_at number recommended

info

Timestamp in milliseconds since Unix epoch representing the first time the user was recorded

created_at: 1754926521690

properties object recommended

info

Custom Customer Properties Examples

User Segmentation

Use the properties object to store custom user attributes, with property names defined by each business as needed, that enable advanced segmentation, personalization, and analytics across your marketing campaigns.

properties: {
customer_type: "returning",
membership_level: "platinum",
preferred_category: ["electronics", "fashion"],
last_purchase_date: "2024-12-15",
average_order_value: "350.00",
payment_method_preference: "card",
registration_date: "2023-06-15"
}

consent object recommended

Examples

{
"event": {
"name": "newsletter_subscribed",
"value": 0,
"currency": "EUR",
"properties": {
"form_location": "footer",
"newsletter_type": "weekly_digest",
"double_optin": true
}
},
"context": {
"url": "https://example.com/blog/ai-trends-2026",
"page_type": "blog_post",
"environment": "prod"
},
"user": {
"email": "[email protected]",
"first_name": "Maria",
"last_name": "Popescu"
},
"consent": {
"analytics": true,
"personalization": true,
"marketing": true
}
}