Sign Up
Fire the sign_up event when a visitor successfully creates a new account on your website — through email signup, social sign-in (Google, Apple, Facebook), magic-link verification, or any other registration flow. This is the canonical signal for account-creation conversions and onboarding-funnel optimization.
Fire the event once when the account is successfully created (record persisted, email verified if your flow requires it). Use event.id for deduplication and include the user object with at least an email so destinations can build user-level conversions and audiences.
This event is the DATA Reshape equivalent of the standard registration 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 —
sign_up(withmethodparameter). - Google Ads — conversion tracking with Enhanced Conversions from
user. - Meta Pixel / Meta Conversions API —
CompleteRegistration(withvalue,currency,content_name). - TikTok Pixel / TikTok Events API —
CompleteRegistration(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 sign_up event accepts the following objects and fields.
event object required
name string required
Use only static value sign_up for event.name. DATA Reshape maps this to sign_up (GA4) and CompleteRegistration (Meta, TikTok) automatically.
name: "sign_up"
value number required
Estimated value of a registered user (e.g. predicted LTV or onboarding bonus). Used for value-based bidding.
value: 50.00
currency string required
Currency code, ISO 4217 three-letter format.
currency: "USD"
id string
Optional unique sign-up ID from your system.
id: "signup_abc123"
properties object recommended
Custom properties such as method (signup mechanism), referral_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 newly registered user. Include id, email, and any captured fields. Drives Advanced Matching, Enhanced Conversions, 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 sign_up for four common registration methods — Email Signup, Google Sign-in, Apple Sign-in and Facebook Sign-in — plus an additional Minimal tab with only the required fields.
- Email Signup
- Google Sign-in
- Apple Sign-in
- Facebook Sign-in
- Minimal
window.reshape = window.reshape || [];
reshape.push({
"event": {
"name": "sign_up",
"value": 50.00,
"currency": "USD",
"id": "signup_abc123",
"properties": {
"method": "email",
"newsletter_opt_in": true,
"referral_source": "organic_search"
}
},
"context": {
"url": "https://example.com/signup",
"page_type": "signup",
"environment": "prod"
},
"user": {
"id": "cust_abc123",
"email": "[email protected]",
"first_name": "Example First Name",
"last_name": "Example Last Name",
"country": "US"
}
});
window.reshape = window.reshape || [];
reshape.push({
"event": {
"name": "sign_up",
"value": 50.00,
"currency": "USD",
"id": "signup_abc123",
"properties": {
"method": "google_oauth",
"newsletter_opt_in": false
}
},
"context": {
"url": "https://example.com/signup",
"page_type": "signup",
"environment": "prod"
},
"user": {
"id": "cust_abc123",
"email": "[email protected]",
"first_name": "Example First Name",
"last_name": "Example Last Name",
"country": "US"
}
});
window.reshape = window.reshape || [];
reshape.push({
"event": {
"name": "sign_up",
"value": 50.00,
"currency": "USD",
"id": "signup_abc123",
"properties": {
"method": "apple_oauth",
"email_relay_used": true
}
},
"context": {
"url": "https://example.com/signup",
"page_type": "signup",
"environment": "prod"
},
"user": {
"id": "cust_abc123",
"email": "[email protected]",
"country": "US"
}
});
window.reshape = window.reshape || [];
reshape.push({
"event": {
"name": "sign_up",
"value": 50.00,
"currency": "USD",
"id": "signup_abc123",
"properties": {
"method": "facebook_oauth"
}
},
"context": {
"url": "https://example.com/signup",
"page_type": "signup",
"environment": "prod"
},
"user": {
"id": "cust_abc123",
"email": "[email protected]",
"first_name": "Example First Name",
"last_name": "Example Last Name",
"country": "US"
}
});
window.reshape = window.reshape || [];
reshape.push({
"event": {
"name": "sign_up",
"value": 50.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 only on successful account creation — wait for the user record to be persisted (and email verified if your flow requires it).
- Include the
methodproperty —email,google_oauth,apple_oauth,facebook_oauth,magic_link,sso, etc. This is what GA4 maps to itsmethodparameter. - Always include the
userobject with an email — enables Advanced Matching, Enhanced Conversions, and identity reconciliation in connected destinations. - Use a stable
user.id— same ID acrosssign_up,login, and subsequent events lets destinations build proper user-journey reports. - Fire server-side from your registration handler — catches users who close the browser before the client-side push fires.