User Updated
Fire the user_updated event when an authenticated user updates any of their profile information — name, address, phone, email, marketing preferences, language, etc. This event keeps identity data in sync between your platform and downstream destinations, and is particularly important for Advanced Matching, Enhanced Conversions, and identity-reconciliation flows where a stale or partial identity record degrades match rates.
Fire the event once per update action, with the user object containing the full updated identity (not just the changed fields) so downstream destinations always have the latest snapshot.
This event is the DATA Reshape equivalent of the standard user-update 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 — no dedicated standard event; mapped as a custom event.
- Meta Pixel / Meta Conversions API — no dedicated standard event; Reshape can send a custom CamelCase event
UserUpdatedwhen connected. Advanced Matching benefits from the refreshed identity. - TikTok Pixel / TikTok Events API — no dedicated standard event; Reshape can send a custom CamelCase event
UserUpdatedwhen connected. Advanced Matching benefits from the refreshed identity. - Other connected destinations — mapped automatically based on each destination's native schema; CRM/email connectors use this to keep profile records in sync.
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 user_updated event accepts the following objects and fields.
event object required
name string required
Use only static value user_updated for event.name. DATA Reshape maps this to a custom event in GA4, and a custom CamelCase event UserUpdated in Meta and TikTok when connected.
name: "user_updated"
value number required
Typically 0 for profile updates.
value: 0
currency string required
Currency code, ISO 4217 three-letter format.
currency: "USD"
id string
Optional update event identifier.
id: "userupd_abc123"
properties object recommended
Custom properties such as update_type (e.g. profile, address, preferences, email), changed_fields, 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 full updated user identity (not just the changed fields). Send the complete snapshot so destinations can refresh their profile records. 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: "example.customer@example.com"
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 user_updated for four common update scenarios — Profile Update, Address Update, Preferences Update and Email Update — plus an additional Minimal tab with only the required fields.
- Profile Update
- Address Update
- Preferences Update
- Email Update
- Minimal
window.reshape = window.reshape || [];
reshape.push({
"event": {
"name": "user_updated",
"value": 0,
"currency": "USD",
"id": "userupd_abc123",
"properties": {
"update_type": "profile",
"changed_fields": ["first_name", "last_name", "phone"]
}
},
"context": {
"url": "https://example.com/account/profile",
"page_type": "account",
"environment": "prod"
},
"user": {
"id": "cust_abc123",
"email": "example.customer@example.com",
"phone": "+10000000000",
"first_name": "Example First Name",
"last_name": "Example Last Name",
"country": "US"
}
});
window.reshape = window.reshape || [];
reshape.push({
"event": {
"name": "user_updated",
"value": 0,
"currency": "USD",
"id": "userupd_abc123",
"properties": {
"update_type": "address",
"changed_fields": ["street", "city", "postal_code"]
}
},
"context": {
"url": "https://example.com/account/addresses",
"page_type": "account",
"environment": "prod"
},
"user": {
"id": "cust_abc123",
"email": "example.customer@example.com",
"phone": "+10000000000",
"first_name": "Example First Name",
"last_name": "Example Last Name",
"country": "US",
"region": "Example Region",
"city": "Example City",
"street": "123 Sample Street",
"postal_code": "00000"
}
});
window.reshape = window.reshape || [];
reshape.push({
"event": {
"name": "user_updated",
"value": 0,
"currency": "USD",
"id": "userupd_abc123",
"properties": {
"update_type": "preferences",
"changed_fields": ["marketing_consent", "preferred_language"]
}
},
"context": {
"url": "https://example.com/account/preferences",
"page_type": "account",
"environment": "prod"
},
"user": {
"id": "cust_abc123",
"email": "example.customer@example.com",
"country": "US",
"properties": {
"marketing_consent": false,
"preferred_language": "en",
"preferred_categories": ["apparel", "accessories"]
}
}
});
window.reshape = window.reshape || [];
reshape.push({
"event": {
"name": "user_updated",
"value": 0,
"currency": "USD",
"id": "userupd_abc123",
"properties": {
"update_type": "email",
"changed_fields": ["email"],
"previous_email_hash": "sha256_of_old_email"
}
},
"context": {
"url": "https://example.com/account/email",
"page_type": "account",
"environment": "prod"
},
"user": {
"id": "cust_abc123",
"email": "example.customer@example.com",
"country": "US"
}
});
window.reshape = window.reshape || [];
reshape.push({
"event": {
"name": "user_updated",
"value": 0,
"currency": "USD"
},
"user": {
"id": "cust_abc123",
"email": "example.customer@example.com"
}
});
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
- Send the full updated identity — include all known user fields, not just the changed ones. Downstream destinations refresh their profile with whatever fields are present.
- Always include the stable
user.id— this is what destinations use to match the update to an existing profile. - Fire once per update action — not on every keystroke. Wait for the form submit / save action.
- Capture
update_typeinproperties— useful for analytics segmentation (which kinds of updates happen most). - Fire server-side from your account-update handler — most reliable, captures the update even if the user navigates away.