Newsletter Subscribed
Fire the newsletter_subscribed event when a visitor opts in to a newsletter, mailing list, product alert, back-in-stock notification, or any equivalent email-based subscription. This is the standard signal for email-list growth and is widely used as a soft-conversion event for top-of-funnel campaigns.
Fire the event once when the subscription is confirmed (after double opt-in if your flow requires it, or immediately on successful submission for single opt-in flows). Always include the user.email since email-list events are useless without the identity.
This event is the DATA Reshape equivalent of the standard subscribe event in every major advertising and analytics platform — push it once and Reshape fans it out to every connected destination with the correct platform-specific name and field mapping, so you do not need to fire gtag, fbq, ttq or other tracking function calls in parallel.
- Google Analytics 4 —
subscribe(withvalue,currency). - Google Ads — conversion tracking when configured as a soft conversion.
- Meta Pixel / Meta Conversions API —
Subscribe(withvalue,currency,predicted_ltv). - TikTok Pixel / TikTok Events API —
Subscribe(withvalue,currency). - Other connected destinations — mapped automatically based on each destination's native schema.
A single Reshape event can produce one or more native events per destination, with different characteristics depending on each website's destination configuration (active pixels, server endpoints, event-mapping rules).
Complete Reference
The newsletter_subscribed event accepts the following objects and fields.
event object required
name string required
Use only static value newsletter_subscribed for event.name. DATA Reshape maps this to subscribe (GA4) and Subscribe (Meta, TikTok) automatically.
name: "newsletter_subscribed"
value number required
Estimated value of a newsletter subscriber (typical: 1–20 USD predicted LTV contribution).
value: 5.00
currency string required
Currency code, ISO 4217 three-letter format.
currency: "USD"
id string
Optional subscription event identifier.
id: "sub_abc123"
properties object recommended
Custom properties such as list_name, placement, signup_source, etc.
context object
url string required-if-applicable
Collected automatically for standard websites. Required only for SPA applications where URL changes don't trigger automatic page context updates.
url:"https://example.com/products/prod_abc123?utm_source=example"
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
Type of page (product, home ...)
page_type: "product"
environment string recommended
Allowed values: prod, dev
environment: "prod"
user object required
The subscriber's identity. Email is required at minimum. Drives Advanced Matching and identity reconciliation in connected destinations. View complete User Object documentation
id string recommended
Unique customer identifier in your system.
id: "cust_abc123"
email string recommended
Customer email address in plaintext. Do not send pre-hashed values — DATA Reshape automatically normalizes and hashes before sending to destinations.
email: "[email protected]"
phone string recommended
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: "+10000000000"
first_name string recommended
Customer first name
first_name: "Example First Name"
last_name string recommended
Customer last name
last_name: "Example Last Name"
country string
Country name or ISO country code
country: "US"
region string recommended
State, province, or region name
region: "Example Region"
city string recommended
City or locality name
city: "Example City"
street string
Street address including number
street: "123 Sample Street"
postal_code string
Postal code or ZIP code
postal_code: "00000"
orders_total_number number recommended
Cumulative number of orders placed by this user
orders_total_number: 5
orders_canceled_number number recommended
Cumulative number of orders placed and canceled by this user
orders_canceled_number: 0
orders_total_value number recommended
Cumulative lifetime user orders value (decimal format: 2500.50)
orders_total_value: 1234.99
orders_refunded_value number recommended
Cumulative lifetime user orders value canceled (decimal format: 2500.50)
orders_refunded_value: 250.99
predicted_value number
Predicted lifetime value of a customer for your business
predicted_value: 100.99
created_at number recommended
Timestamp in milliseconds since Unix epoch representing the first time the user was recorded
created_at: 1754926521690
properties object recommended
Custom Customer Properties Examples
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.
- E-commerce Customer
- B2B Lead/Customer
- Subscription Service
- Content Platform
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"
}
properties: {
company_size: "enterprise",
industry: "fintech",
job_title: "marketing_director",
decision_maker: "true",
budget_range: "50000-100000",
lead_source: ["linkedin", "webinar"],
qualification_status: "qualified",
sales_stage: "proposal"
}
properties: {
subscription_tier: "premium",
billing_cycle: "annual",
feature_usage: ["analytics", "reporting", "api"],
trial_user: "false",
renewal_date: "2025-06-30",
support_level: "priority",
usage_frequency: "daily"
}
properties: {
content_preferences: ["technology", "business"],
engagement_level: "high",
newsletter_subscriber: "true",
social_media_follower: "true",
content_consumption: "premium",
device_preference: ["mobile", "desktop"],
timezone: "Example/Timezone"
}
Examples
The examples below show how to push newsletter_subscribed for four common subscription scenarios — Newsletter, Product Alert, Back-in-stock Alert and Price Drop Alert — plus an additional Minimal tab with only the required fields.
- Newsletter
- Product Alert
- Back-in-stock Alert
- Price Drop Alert
- Minimal
window.reshape = window.reshape || [];
reshape.push({
"event": {
"name": "newsletter_subscribed",
"value": 5.00,
"currency": "USD",
"id": "sub_abc123",
"properties": {
"list_name": "general_newsletter",
"placement": "footer",
"signup_source": "homepage"
}
},
"context": {
"url": "https://example.com/",
"page_type": "home",
"environment": "prod"
},
"user": {
"email": "[email protected]",
"first_name": "Example First Name",
"country": "US"
}
});
window.reshape = window.reshape || [];
reshape.push({
"event": {
"name": "newsletter_subscribed",
"value": 8.00,
"currency": "USD",
"id": "sub_abc123",
"properties": {
"list_name": "new_product_alerts",
"placement": "product_page",
"interest_category": "electronics"
}
},
"context": {
"url": "https://example.com/products/wireless-headphones-black",
"page_type": "product",
"environment": "prod"
},
"user": {
"email": "[email protected]",
"country": "US"
}
});
window.reshape = window.reshape || [];
reshape.push({
"event": {
"name": "newsletter_subscribed",
"value": 12.00,
"currency": "USD",
"id": "sub_abc123",
"properties": {
"list_name": "back_in_stock",
"placement": "out_of_stock_modal",
"product_id": "prod_tshirt_navy_m",
"product_name": "Example Cotton T-Shirt - Navy / M"
}
},
"context": {
"url": "https://example.com/products/cotton-tshirt-navy-m",
"page_type": "product",
"environment": "prod"
},
"user": {
"email": "[email protected]",
"country": "US"
}
});
window.reshape = window.reshape || [];
reshape.push({
"event": {
"name": "newsletter_subscribed",
"value": 10.00,
"currency": "USD",
"id": "sub_abc123",
"properties": {
"list_name": "price_drop_alerts",
"placement": "product_page",
"product_id": "prod_laptop_15_512",
"current_price": 1099.99,
"alert_below_price": 999.00
}
},
"context": {
"url": "https://example.com/products/laptop-15-512",
"page_type": "product",
"environment": "prod"
},
"user": {
"email": "[email protected]",
"country": "US"
}
});
window.reshape = window.reshape || [];
reshape.push({
"event": {
"name": "newsletter_subscribed",
"value": 5.00,
"currency": "USD"
},
"user": {
"email": "[email protected]"
}
});
Custom properties (event.properties, user.properties, products[*].properties) are fully processed server-side. On browser-side pixels and tags, only a subset may be available. Server-side processing can also enrich the outgoing payload with additional parameters derived from context and data quality.
Best Practices
- Fire after subscription confirmation — for double opt-in flows, fire on email confirmation, not on initial form submit (otherwise you count unconfirmed subscribers as conversions).
- Always include the
user.email— newsletter events without an email are useless. Email is the identity for every email-platform destination. - Use a small but non-zero
event.value— even 1–5 USD enables value-based bidding to favor users likely to subscribe. - Capture
list_nameandplacementinproperties— critical for segmenting which lists/placements drive the most valuable subscribers. - Fire server-side from your subscription handler — most reliable for double-opt-in confirmation flows.