Difference between revisions of "ATC/Current/SDK/Record"

From Genesys Documentation
Jump to: navigation, search
m (Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2")
 
(9 intermediate revisions by 3 users not shown)
Line 6: Line 6:
 
|Dimension=DevTracking
 
|Dimension=DevTracking
 
|ComingSoon=No
 
|ComingSoon=No
−
|Platform=GenesysEngage-cloud, PureConnect, GenesysCloud
+
|Platform=PureConnect, GenesysCloud, GenesysEngage-cloud
 
|Section={{Section
 
|Section={{Section
 +
|alignment=Vertical
 +
|structuredtext={{NoteFormat|1=This article only applies to customers using {{Link-AnywhereElse|product=ATC|version=Current|manual=AdminGuide|topic=About_web_chats|display text=web chat}}. If you are a Genesys Cloud CX customer, we encourage you to use the new {{Link-AnywhereElse|product=ATC|version=Current|manual=AdminGuide|topic=About_web_messaging|display text=web messaging}} feature to replace web chat.|2=}}<br />
 +
|Status=No
 +
}}{{Section
 
|sectionHeading=Description
 
|sectionHeading=Description
 
|alignment=Vertical
 
|alignment=Vertical
Line 28: Line 32:
 
|anchor=eventName
 
|anchor=eventName
 
|alignment=Vertical
 
|alignment=Vertical
−
|structuredtext=*Description: name of the custom event
+
|structuredtext=*'''Description:''' Name of the custom event
−
*Type: string
+
*'''Type:''' String
−
*Status: required
+
*'''Status:''' Required
 +
*'''Restrictions''': See {{Link-SomewhereInThisVersion|manual=SDK|topic=Types_of_tracked_data|anchor=Guidelines|display text=Guidelines for custom event names}}.
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
Line 36: Line 41:
 
|anchor=customAttributes
 
|anchor=customAttributes
 
|alignment=Vertical
 
|alignment=Vertical
−
|structuredtext=*Description: adds extra information to <tt>pageview</tt> event
+
|structuredtext=*'''Description:''' Adds extra information to <code>pageview</code> event
−
*Type: object
+
*'''Type:''' Object
−
*Status: optional
+
*'''Status:''' Optional
−
*Restrictions: a flat object with properties of type string, number, or boolean
+
*'''Restrictions:''' Flat object with properties of type string, number, Boolean, or customAttribute
  
−
==== Example ====
+
====Example====
 
<code>ac('record', 'product_added', { price: 15.99, code: 'CDE-123', name: 'Product', hasBatteries: false });</code>
 
<code>ac('record', 'product_added', { price: 15.99, code: 'CDE-123', name: 'Product', hasBatteries: false });</code>
 +
 +
Additionally, define the datatype for the attribute to define the value better.
 +
====Example====
 +
<code>ac('record', 'product_added', { price: {datatype: 'integer' value: 15, name: {datatype: 'string' value: 'Product'}‎​}​​});​ </code>
 +
|Status=No
 +
}}{{Section
 +
|sectionHeading=customAttributes for outcome value tracker
 +
|anchor=outcome_value
 +
|alignment=Vertical
 +
|structuredtext=To derive the value of an outcome, create an event that comprises an associated value field. Then, using this event and the value field (within the same event), track the value of {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Manage_outcomes|display text=the outcome you created.}} 
 +
 +
For example, the following event tracks the products added with the value, price''.'' When you create an outcome using this event, the products added along with their value is tracked as part of the outcome. 
 +
 +
*'''Description:''' Adds extra information to <code>pageview</code> event
 +
*'''Type:''' Object
 +
*'''Status:''' Optional
 +
*'''Restrictions:''' Flat object with properties of type string, number, or Boolean
 +
 +
====Example====
 +
<code>ac('record', 'product_added', { price: 15, code: 'CDE-123', name: 'Product', hasBatteries: false });</code>
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
 
|sectionHeading=options
 
|sectionHeading=options
 
|alignment=Vertical
 
|alignment=Vertical
−
|structuredtext=*Description: Used for additional configuration
+
|structuredtext=*'''Description:''' Used for more configuration
−
*Type: object
+
*'''Type:''' Object
−
*Status: optional
+
*'''Status:''' Optional
−
*Properties:
+
*'''Properties:''' See the following table.
  
 
{{{!}} class="wikitable"
 
{{{!}} class="wikitable"
Line 61: Line 86:
 
{{!}}-
 
{{!}}-
 
{{!}}{{!}}traitsMapper
 
{{!}}{{!}}traitsMapper
−
{{!}}{{!}}used to map custom attributes to traits. For more information, see {{Link-SomewhereInThisVersion|manual=SDK|topic=Traits_mapper|display text=Traits Mapper.}}
+
{{!}}{{!}}Used to map custom attributes to traits. For more information, see {{Link-SomewhereInThisVersion|manual=SDK|topic=Traits_mapper|display text=Traits Mapper.}}
 
{{!}}{{!}}traitsMapper
 
{{!}}{{!}}traitsMapper
 
{{!}}{{!}}<br />
 
{{!}}{{!}}<br />
Line 67: Line 92:
 
{{!}}-
 
{{!}}-
 
{{!}}{{!}}callback
 
{{!}}{{!}}callback
−
{{!}}{{!}}called once beacon is sent
+
{{!}}{{!}}Called once beacon is sent
 
{{!}}{{!}}function
 
{{!}}{{!}}function
 
{{!}}{{!}}optional
 
{{!}}{{!}}optional

Latest revision as of 11:30, February 7, 2024

This topic is part of the manual Journey JavaScript SDK for version Current of Genesys Predictive Engagement.

Learn how to use the record method to capture website events.

Important
This article only applies to customers using web chat. If you are a Genesys Cloud CX customer, we encourage you to use the new web messaging feature to replace web chat.

Description

The record method records custom website events.

Signature

ac('record', eventName, [customAttributes], [options])

Arguments

eventName

customAttributes

  • Description: Adds extra information to pageview event
  • Type: Object
  • Status: Optional
  • Restrictions: Flat object with properties of type string, number, Boolean, or customAttribute

Example

ac('record', 'product_added', { price: 15.99, code: 'CDE-123', name: 'Product', hasBatteries: false });

Additionally, define the datatype for the attribute to define the value better.

Example

ac('record', 'product_added', { price: {datatype: 'integer' value: 15, name: {datatype: 'string' value: 'Product'}‎​}​​});​ 

customAttributes for outcome value tracker

To derive the value of an outcome, create an event that comprises an associated value field. Then, using this event and the value field (within the same event), track the value of the outcome you created.

For example, the following event tracks the products added with the value, price. When you create an outcome using this event, the products added along with their value is tracked as part of the outcome.

  • Description: Adds extra information to pageview event
  • Type: Object
  • Status: Optional
  • Restrictions: Flat object with properties of type string, number, or Boolean

Example

ac('record', 'product_added', { price: 15, code: 'CDE-123', name: 'Product', hasBatteries: false });

options

  • Description: Used for more configuration
  • Type: Object
  • Status: Optional
  • Properties: See the following table.
Name Description Type Status Default
traitsMapper Used to map custom attributes to traits. For more information, see Traits Mapper. traitsMapper

callback Called once beacon is sent function optional
callbackTimeout ms to wait for beacon to send number optional
Retrieved from "https://all.docs.genesys.com/ATC/Current/SDK/Record (2025-07-14 15:45:06)"
Comments or questions about this documentation? Contact us for support!