Skip to main content

Click Interaction

Fire the click event to track meaningful click interactions on your website — buttons, links, downloads, video controls, social-share icons, and any other clickable element that signals user engagement. This is a generic interaction event for any click that doesn't have a more specific event (click_to_phone, click_to_email, click_to_whatsapp are auto-tracked separately).

Fire the event once per click, with event.properties capturing what was clicked. The richer the properties (element name, action, target, position), the more useful the data for analytics segmentation.

This event is the DATA Reshape equivalent of the standard click 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 click event. Properties become custom event params.
  • Google Ads — typically not used as a conversion; can be configured for engagement-based audiences.
  • Meta Pixel / Meta Conversions API — no dedicated standard event; Reshape can send a custom CamelCase event Click when connected.
  • TikTok Pixel / TikTok Events API — no dedicated standard event; Reshape can send a custom CamelCase event Click when connected.
  • Other connected destinations — mapped automatically based on each destination's native schema.
One push, many native events

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 click event accepts the following objects and fields.

event object required

name string required

info

Use only static value click for event.name.

name: "click"

value number required

info

Typically 0 for generic clicks. Use a non-zero value for engagement-based scoring (e.g. download click might be worth more than a button click).

value: 0

currency string required

info

Currency code, ISO 4217 three-letter format.

currency: "USD"

id string

info

Optional click event identifier.

id: "click_abc123"

properties object recommended

info

Custom properties describing what was clicked — element_name, element_action, element_target, element_position, etc. The richer the properties, the more useful for analytics segmentation.

context object

info
View complete Context Object documentation

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://example.com/products/prod_abc123?utm_source=example"
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 recommended

info
View complete User Object documentation

id string recommended

info

Unique customer identifier in your system.

id: "cust_abc123"

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.

email: "[email protected]"

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: "+10000000000"

first_name string recommended

info

Customer first name

first_name: "Example First Name"

last_name string recommended

info

Customer last name

last_name: "Example Last Name"

country string

info

Country name or ISO country code

country: "US"

region string recommended

info

State, province, or region name

region: "Example Region"

city string recommended

info

City or locality name

city: "Example City"

street string

info

Street address including number

street: "123 Sample Street"

postal_code string

info

Postal code or ZIP code

postal_code: "00000"

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"
}

Examples​

The examples below show how to push click for five common element types — Button, Link, Download, Video and Social Share — plus an additional Minimal tab with only the required fields.

window.reshape = window.reshape || [];
reshape.push({
  "event": {
    "name": "click",
    "value": 0,
    "currency": "USD",
    "properties": {
      "element_type": "button",
      "element_name": "request_demo",
      "element_action": "submit_intent",
      "element_position": "hero_section",
      "element_label": "Request a Demo"
    }
  },
  "context": {
    "url": "https://example.com/",
    "page_type": "home",
    "environment": "prod"
  }
});
Custom properties

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​

  • Be selective — track only meaningful clicks that have analytic or attribution value. Tracking every click pollutes data and inflates event counts.
  • Use consistent element_type values — button, link, download, video, social_share, image, icon, etc. Consistent typing produces clean reports across destinations.
  • Capture element_name — a stable, semantic name for the clicked element (e.g. request_demo, footer_pricing, pricing_guide_pdf). This is what destinations use for segmentation.
  • Use value for engagement scoring — assign higher values to clicks that signal stronger intent (downloads, video plays > generic link clicks).
  • For phone/email/WhatsApp clicks, use the dedicated auto-tracked events — click_to_phone, click_to_email, click_to_whatsapp are fired automatically by DATA Reshape and do not need manual pushing.