Contents

# TalonOne::EventV2

## Properties

Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
**profile_id** | **String** | ID of the customer profile set by your integration layer.  **Note:** If the customer does not yet have a known `profileId`, we recommend you use a guest `profileId`.  | [optional] 
**store_integration_id** | **String** | The integration ID of the store. You choose this ID when you create a store. | [optional] 
**evaluable_campaign_ids** | **Array<Integer>** | When using the `dry` query parameter, use this property to list the campaign to be evaluated by the Rule Engine.  These campaigns will be evaluated, even if they are disabled, allowing you to test specific campaigns before activating them.  | [optional] 
**type** | **String** | A string representing the event name. Must not be a reserved event name. You create this value when you [create an attribute](https://docs.talon.one/docs/dev/concepts/entities/events#creating-a-custom-event) of type `event` in the Campaign Manager.  | 
**attributes** | [**Object**](.md) | Arbitrary additional JSON properties associated with the event. They must be created in the Campaign Manager before setting them with this property. See [creating custom attributes](https://docs.talon.one/docs/product/account/dev-tools/managing-attributes#creating-a-custom-attribute). | [optional] 

## Code Sample

```ruby
require 'TalonOne'

instance = TalonOne::EventV2.new(profile_id: URNGV8294NV,
                                 store_integration_id: STORE-001,
                                 evaluable_campaign_ids: [10, 12],
                                 type: pageViewed,
                                 attributes: {"myAttribute":"myValue"})
```

Version data entries

3 entries across 3 versions & 1 rubygems

Version	Path
talon_one-7.0.0	docs/EventV2.md
talon_one-6.0.0	docs/EventV2.md
talon_one-5.0.0	docs/EventV2.md