There are some event properties that are present in most of the events we track:

  • client.domain - domain the user was at when event occurred
  • client.referrer - where the user arrived from (eg. Google)
  • client.title - the page title that appears in the browser tab
  • client.type - eg. web/fia/amp
  • client.url - url the user was at when event occurred
  • client.user_agent - browser the user was on when event occured

However a lot of these events have a few extra properties:

Standard Events

Form Submission

  • form.action - url the user was at when event occurred
  • form.id - the id you have given the form to help identify it
  • form.method - GET/POST 
  • form.properties.name - the name you have given the form to help identify it
  • form.properties.value - the information inputted by the user

Link Click

  • dest_url - the landing url when a link was clicked

Pageview

  • content.article.authors - author of the article
  • content.article.category - category the article falls into (if set)
  • content.article.type - type the article falls into (if set)
  • content.description - description given to article (if set)
  • content.headline - headline of the article
  • content.product.make - eg. BMW/Audi
  • content.product.name - eg. BMW M4
  • content.product.price - price listed on page as integer
  • content.product.type - eg. Hatchback
  • content.review.rating - review listed on page as integer eg. 4.5
  • content.type - eg. Review/Article etc
  • geo_info.city - user city
  • geo_info.continent - user continent
  • geo_info.country - user country
  • geo_info.postal_code - user post code
  • geo_info.province - user province
  • ip_address - user IP address
  • isp_info.autonomous_system_number - internet service provider ASN
  • isp_info.autonomous_system_organization - eg. Virgin Media Limited, British Telecommunications PLC
  • isp_info.isp - internet service provider eg. Virgin Media, BT
  • isp_info.organization - same as isp
  • publisher.name - different publishers in a project
  • visit.id - ID specific to visit

Pageview Engagement

  • completion - how far down page a user scrolled (decimal figure)
  • engaged_time - always 5 per event

Reaction (only available for analytics)

  • reaction_id - ID specific to reaction that caused the event
  • type - type of reaction eg. impression
  • variant_id - ID specific to reaction that caused the event

Segment Entry and Segment Exit

  • custom_id - mostly 'null' unless set
  • segment_id - long ID specific to segment that caused the event
  • segment_name - eg. Everyone
  • segment_number - segment code (seen in 'Segments' tab)

Slot Clicked and Slot Rendered (collected from DFP - only available for analytics)

  • advertiser_id - unique to campaign, found in DFP
  • campaign_id - unique to campaign, found in DFP
  • creative_id - unique to campaign, found in DFP
  • height - slot height
  • is_empty - true or false, slot returned without creative
  • line_item_id - unique to campaign, found in DFP
  • service_name - set to 'publisher_ads' if from DFP
  • slot.ad_unit_path - unique to campaign, found in DFP
  • slot.slot_element_id - unique to campaign, found in DFP
  • slot.targeting_keys.key - unique to campaign, set in DFP
  • slot.targeting_keys.value - unique to campaign, set in DFP
  • width - slot width

Custom Events


Gigya Profile

  • age - user age
  • birth_year - user birth year
  • gender - male/female

Please note, some properties may vary depending on the project.

If you have any questions, please do not hesitate to contact support@permutive.com.

Did this answer your question?