Phone number of the user associated with the action. E.164 format is required. This field is required if email is not provided.

User associated with the action. Note that this is a visitor to the site and does not need to be actively subscribed to Attentive.

Expects a URL: http://my.cdn.com/products/new-product.png

Expects a URL: http://my-store.com/products/shirts/my-shirt

The price of the product.

Example: USD for U.S. Dollars.

Timestamp of when the action occurred in ISO 8601 format. If the timestamp is older than 12 hours, it will not trigger any relevant journeys. If no timestamp is provided, it is assumed the event occurred when the endpoint is called.

Phone number of the user associated with the action. E.164 format is required. This field is required if email is not provided.

User associated with the action. Note that this is a visitor to the site and does not need to be actively subscribed to Attentive.

The type of event. This name is case sensitive. "Order shipped" and "Order Shipped" would be considered different event types.

Any metadata associated with the event. Object keys are expected to be strings, and cannot contain any of the following special characters single quote ' double quote " curly braces { } square brackets backslash \ comma , Object values can be any type. Note that both object keys and object values are case sensitive. For example, "deliverydate" and "DeliveryDate" would be considered different event properties. For URLs that are provided as a value, Attentive will automatically shorten the link with your brand's link shortener. For example, https://mysite.com/.

A unique identifier representing this specific event. A UUID is recommended.

Timestamp of when the action occurred in ISO 8601 format. If the timestamp is older than 12 hours, it will not trigger any relevant Journeys. If no timestamp is provided, it is assumed the event occurred when the endpoint is called.

Phone number of the user associated with the action. E.164 format is required. This field is required if email is not provided.

User associated with the action. Note that this is a visitor to the site and does not need to be actively subscribed to Attentive.

The unique identifier of the sign-up source. Contact our White Glove team (whiteglove@attentivemobile.com) or your Client Strategy Manager at Attentive to request a sign-up source for either marketing or transactional opt-ins. Our team will verify that you implemented the endpoint with compliant legal disclosure language.

Phone number of the user associated with the action. E.164 format is required. This field is required if email is not provided.

User associated with the action. Note that this is a visitor to the site and does not need to be actively subscribed to Attentive.

Expects a URL: http://my.cdn.com/products/new-product.png

Expects a URL: http://my-store.com/products/shirts/my-shirt

The price of the product.

Example: USD for U.S. Dollars.

Timestamp of when the action occurred in ISO 8601 format. If the timestamp is older than 12 hours, it will not trigger any relevant journeys. If no timestamp is provided, it is assumed the event occurred when the endpoint is called.

Phone number of the user associated with the action. E.164 format is required. This field is required if email is not provided.

A user's email we use to fetch subscription eligibility.

This field is optional when email is filled in - make sure this channel is enabled on Fuzey platform before using it.

This field is optional when phone number is filled in - make sure this channel is enabled on Fuzey platform before using it.

Tags are a simple and useful way to identify customers on Fuzey's platform. You might want to assign tags to customers that allow you to make an easy and clear distinction of where and when they were generated (e.g facebook_campaign_xmas).

Along with the customer creation a conversation is also opened on Fuzey's platform. This message is meant to help agents to identify where the lead was generated from so that they have all that they need in order to carry on with customer service (E.g Hello there, I've just filled in xmas campaign card on facebook marketing campaign for a 20% discount voucher)

Phone number of the user associated with the action. E.164 format is required. This field is required if email is not provided.

User associated with the action. Note that this is a visitor to the site and does not need to be actively subscribed to Attentive.

Any metadata associated with the attribute. Object keys are expected to be strings. Object values can be any type. Both object keys and object values are case sensitive. "Favorite color" and "Favorite Color" would be considered different custom attributes.

Email of a subscriber. Only required if subjectPhoneNumber is empty.

Email of a subscriber. Only required if subjectEmail is empty.

An optional message for an audit trail.

Phone number of the user associated with the action. E.164 format is required. This field is required if email is not provided.

User associated with the action. Note that this is a visitor to the site and does not need to be actively subscribed to Attentive.

Examples: "MARKETING", "TRANSACTIONAL"

Phone number of the user associated with the action. E.164 format is required. This field is required if email is not provided.

User associated with the action. Note that this is a visitor to the site and does not need to be actively subscribed to Attentive.

Expects a URL: http://my.cdn.com/products/new-product.png

Expects a URL: http://my-store.com/products/shirts/my-shirt

The price of the product.

Example: USD for U.S. Dollars.

Timestamp of when the action occurred in ISO 8601 format. If the timestamp is older than 12 hours, it will not trigger any relevant journeys. If no timestamp is provided, it is assumed the event occurred when the endpoint is called.

This is the number with whatsapp activated that you enabled on Fuzey's platform.

Please be aware that if you send a message to a number that does not have whatsapp activated, the message will fail on Fuzey's platform.