# Import Website Actions

It is very easy to import website data tracked outside of the HockeyStack website tracking snippet. Below we outline the general schema needed and example of what the data would like in your warehouse.

Website actions import currently supports only pageviews and not other website actions (like form submissions and web clicks).

### Example Schema

All column names should be in underscores.

<table data-full-width="true"><thead><tr><th width="177.984375">Column Name</th><th width="312.84765625">Example Value</th><th width="129.296875">Requirement<select><option value="9tyl8LmTwffx" label="required" color="blue"></option><option value="4DkcRNYCW7fk" label="recommended" color="blue"></option></select></th><th>Description</th></tr></thead><tbody><tr><td>identity</td><td>person@company.com</td><td><span data-option="9tyl8LmTwffx">required</span></td><td>Identifier column. email address or company domain</td></tr><tr><td>date</td><td>2025-03-18T12:58:01.000Z</td><td><span data-option="9tyl8LmTwffx">required</span></td><td>The timestamp of the website action</td></tr><tr><td>page_url</td><td>https://example.com/blog/article-1?utm_source=facebook&#x26;utm_medium=organic&#x26;utm_campaign=brand_awareness&#x26;utm_content=video_ad_1&#x26;utm_term=coso</td><td><span data-option="9tyl8LmTwffx">required</span></td><td>Current full page associated with the pageview (should include UTM parameters if possible)</td></tr><tr><td>referrer</td><td><a href="https://facebook.com">https://facebook.com</a></td><td><span data-option="9tyl8LmTwffx">required</span></td><td>The URL of the webpage from which a user clicked a link to arrive at the website</td></tr><tr><td>user_id</td><td>684748833</td><td><span data-option="4DkcRNYCW7fk">recommended</span></td><td>Contact or company id from CRM or other sources. provides additional identifier information</td></tr><tr><td>company_domain</td><td>company.com</td><td></td><td>Can be its own separate column if identity is an email address</td></tr><tr><td>utm_source</td><td></td><td></td><td>Only necessary if page_url does not include UTM parameters</td></tr><tr><td>utm_medium</td><td></td><td></td><td>Only necessary if page_url does not include UTM parameters</td></tr><tr><td>utm_campaign</td><td></td><td></td><td>Only necessary if page_url does not include UTM parameters</td></tr><tr><td>utm_content</td><td></td><td></td><td>Only necessary if page_url does not include UTM parameters</td></tr><tr><td>utm_term</td><td></td><td></td><td>Only necessary if page_url does not include UTM parameters</td></tr><tr><td>engagement_type</td><td>Direct</td><td></td><td>This will be saved as an action property</td></tr><tr><td>contact_name</td><td>Someone Everyone</td><td></td><td>This will be saved as an action property</td></tr></tbody></table>

### UTM Parameters

The 5 standard UTM parameters are UTM Source, UTM Medium, UTM Campaign, UTM Content and UTM Term.

They should ideally be included in page\_url but if they are defined as separate columns, the import will automatically concatenate them to the page\_url. Other UTM parameters would be usable as action properties.

### Action Properties

These are extra information to describe a website action, such as session information or other properties from your data source. Any column name that doesn't map to a specified column in the given schema example will be ingested as an action property.