Event Propensity table

An Event Propensity table associates individual customers to the events that, depending on the type of event, are most likely to lead to engagement with your brand.

Note

The size of the Event Propensity table in your tenant is determined by the number of customers who are associated with events in the table.

Important

The Unified Product Catalog table represents the taxonomy for your products and brands. Attributes are added to the Unified Product Catalog table when pc/ semantic tags are applied to your data sources. All pc/ semantic tags are optional. Use the ones that best define the shape of your product catalog and best describe the individual items within it. The product ID is used as an input to predictive modeling.

Add the Event Propensity table

An Event Propensity table associates individual customers to the events that, depending on the type of event, are most likely to lead to engagement with your brand.

To add a Event Propensity table you must extend the customer 360 database to add a table that joins the Event Propensity ProductAttribute passthrough table to the Event Propensity Audience ProductAttribute passthrough table.

To add the Event Propensity table

1. From the Customer 360 page, under All Databases, select the menu for the customer 360 database, and then click Edit.

2. From the Database Editor, click Add Table.

3. Name the table “Event Propensity” (or some other name that clearly identifies this table as the event propensity table for your tenant).

4. Set the build mode to SQL.

5. Add the following SQL:

   SELECT
     r.product_attribute AS `product_sub_category`
     ,r.amperity_id
     ,r.score
     ,r.ranking
     ,r.ranking <= s.audience_size_small AS audience_size_small
     ,r.ranking <= s.audience_size_medium AS audience_size_medium
     ,r.ranking <= s.audience_size_large AS audience_size_large
   FROM Predicted_Affinity_ProductAttribute AS r
   LEFT JOIN Predicted_Affinity_Audience_ProductAttribute AS s
   ON r.product_attribute = s.product_attribute
   

6. Click Validate to verify the SQL runs without error.

7. Click Next. This opens the Database Table Definition page.

8. Add a table description. This enables a tooltip that is visible from other areas in Amperity.

9. Verify that the db/required and db/unique database field semantics were applied to the amperity_id column.

10. Under Version History, select Enable table version history.

11. Click Save.

Column reference

The Event Propensity table contains the following columns:

Column name	Data type	Description
Amperity ID	String	The unique identifier that is assigned to clusters of customer records that all represent the same individual. The Amperity ID does not replace primary and foreign keys, but exists alongside them within unified profiles. Note The Amperity ID is a universally unique identifier (UUID) that is represented by 36 characters spread across five groups separated by hyphens: 8-4-4-4-12. For example: 123e4567-e89b-12d3-a456-426614174000
Audience Size Large	Boolean	A flag that indicates the recommended audience size. When this value is True the recommended audience size is large. A large audience is predicted to include ~90% of future purchasers, while also including a high number of non-purchasers.
Audience Size Medium	Boolean	A flag that indicates the recommended audience size. When this value is True the recommended audience size is medium. A medium audience is predicted to include ~70% of future purchasers, though it may also include a moderate number of non-purchasers.
Audience Size Small	Boolean	A flag that indicates the recommended audience size. When this value is True the recommended audience size is small. A small audience is predicted to include ~50% of future purchasers, while including the fewest non-purchasers. Use a small audience size to help prevent wasted spend and reduce opt-outs.
Ranking	Integer	A ranking of customers by their score for this event. A rank that is less than or equal to X will provide the top N customers with an propensity for this event.
Score	Float	The strength of a customers’s propensity for this event, shown as an uncalibrated probability. Tip The score is used internally by Amperity, does not directly correlate to ranking and/or audience size, and should not be used in segments. Sort results by Ranking, and then compare those results to audience sizes. Higher rankings within smaller audience sizes correlate with higher propensity.
Target Value	Integer
Revenue Event Days Since Last Event	Integer