Event Bulk Tracking (β)¶

This feature lets you treat actions performed and status changes for multiple users as events and bulk import them into Repro via CSV.

Reference¶

Please refer to the following for basic usage of events.

Track events

If you will track events via the SDK instead of this feature, see the documents below.

Get Started¶

Event bulk tracking is an optional feature. If you wish to use it, please contact us via the chat at the bottom right of the dashboard or reach out to your sales representative.

CSV files¶

Event bulk tracking imports events using a CSV file.

File format¶

user_id,event_name,event_properties
123456,event_1,"{""key1"":""value1"",""key2"":""value2""}"
234567,event_2,"{""key1"":""value1"",""key2"":""value2""}"

File format details¶

Character encoding: UTF-8
Line ending: LF
Header: user_id,event_name,event_properties

Field details¶

Name	Type	Max length	Required	Description
user_id	string	191 characters	✅	Specify the User ID for which you want to register an event in Repro. If the specified user ID does not exist, the user will be created.
event_name	string	191 characters	✅	Event name (details below)
event_properties	string	10kB [1]		Escaped JSON string of the event properties. According to RFC4180, wrap the entire `event_properties` value in double quotes and escape inner double quotes by doubling them. Example: "{""key1"":""value1"",""key2"":""val2""}"

[1]	Event property keys can be up to 48 characters and values up to 191 characters; total per event up to 10KB.

Event data that has been tracked at least once on Repro¶

Only events displayed in the event list with the toggle set to On can be registered. If import fails, check that the target event's toggle is not Off.

Value to set for event_name¶

For events already tracked in Repro, set event_name to the event name shown in the list on the Events > Event settings screen (red box).

Creating a new event¶

Event names starting with ___repro___ cannot be registered or tracked.
If the specified event_name does not exist, it is created and the display name uses that event_name (can be changed later in Events > Event settings).
Creation constraints follow the custom event specification.
- If a value does not meet the specification, registration fails. See the 'Custom Event Specification' section in Event Tracking.
- If the number of registrable events is exceeded, the event name is added but set to Off and is not recorded when users track it.

Event properties¶

The JSON format allowed for event properties is as follows:
- key: String only (max 48 characters)
- value: String only (max 191 characters)
- Up to 10KB total per event
See also: Event Tracking

Usage¶

Upload from dashboard (app.repro.io)¶

From the left navigation bar click 'Events' then open 'Data Import (β)'.

Click 'Upload CSV File', select the CSV containing the events to import, and upload it.

After a successful upload a notification appears and asynchronous processing starts.

When processing finishes, a completion email is sent.

Uploading a CSV file to S3¶

You can upload a CSV directly to the Amazon S3 bucket provided by Repro to run the import. An S3 access key is required.

Access key issuance procedure

In the dashboard open Settings > Project settings.
Switch to the 'Credentials' tab and click 'Add AMAZON S3 Access Key'.

Store the displayed 'Access Key ID' and 'Secret Access Key' in a secure location (the secret cannot be shown again once the popup is closed).

Important

If the 'Amazon S3 Access Key' section does not appear on the project settings screen, contact Customer Success.

Note

After issuing the key, the Access Key ID also appears on the 'Data Import (β)' screen.

S3 bucket and path¶

Bucket name: repro-data-store
Path format: /$YOUR_APP_ID/event_bulk_tracking/YOUR_EVENT_FILE.csv

For $YOUR_APP_ID, specify the App ID displayed on the 'Data Import (β)' screen.

For YOUR_EVENT_FILE.csv, specify the filename to be uploaded.

AWS CLI upload example¶

S3 URI: s3://repro-data-store/$YOUR_APP_ID/event_bulk_tracking/YOUR_EVENTS_FILE.csv

$ aws s3 cp YOUR_EVENTS_FILE.csv s3://repro-data-store/$YOUR_APP_ID/event_bulk_tracking/YOUR_EVENTS_FILE.csv

Limits / recommendations when uploading to S3¶

Restrictions¶

File names cannot contain spaces.
File names cannot contain /.
File text encoding must be UTF-8.

Recommendations¶

Import will proceed in the following cases, but behavior is not guaranteed.

Same file name as a file already imported
File name contains non-alphanumeric characters
Re-upload within 5 minutes of the previous upload

Processing details¶

Based on the uploaded CSV, multiple event data entries are imported into Repro in bulk. Processing is asynchronous; when it finishes, the result is emailed to all members who have 'Settings > Email notifications' turned on.

If an error occurs, you can download a CSV containing the error rows (with reasons) via the link in the email.

Error CSV file

The format of the CSV file downloaded from the import failure email link is as follows:

user_id event_name event_properties

user_id
Event name

Event properties

Failure reasons

user_id	event_name	event_properties
user_id	Event name	Event properties	Failure reasons

Error CSV example

user_id,event_name,event_properties
,ebt-sample,,"'user_id' が不正な値です"

Limitations¶

Event data import processing runs asynchronously.
- We do not guarantee the time from upload completion until the import process starts.
- We do not guarantee a maximum time to completion.
- Because the time from invocation to firing is not guaranteed, if you use this as a cancellation event for event-triggered pushes, ensure sufficient wait time on the push side. Although not guaranteed, waiting at least 30 minutes reduces the risk of sending push notifications to unintended users.
Event bulk tracking is intended for firing multiple events at once. Using it to fire only a single event each time is outside the intended use; please consult Customer Success if you require that usage pattern.
CSV files are subject to the following limits.
- Maximum number of event data records
  
  The maximum number of event data records per file is 1 million.
  
  If the limit is exceeded, import processing fails.
  
  The maximum record count may change in the future.
- Maximum file size
  
  When uploading from app.repro.io, the maximum file size per file is 150MB.
  
  If the limit is exceeded, the file cannot be uploaded and import processing does not start.
  
  When uploading directly to the S3 bucket, the maximum file size per file is 500MB.
  
  The maximum size may change in the future.

Other¶

As a beta offering, use requires agreement to the Repro Beta Test Service Terms.

Note

Specifications and limits are subject to change without notice.