Scheduled Reports

Scheduled Reports let you automate the delivery of Yoodli data on a set schedule. This makes it easier to work with your data in external tools or data warehouses.

Why use Scheduled Reports
If you regularly analyze Yoodli data outside the platform, downloading reports manually can be repetitive and time-consuming. Scheduled Reports save time by automatically sending the data you need, when you need it.

What kind of reports can I Schedule and where?
Org admins can set up automated report deliveries, specifying both the report type and where it should be sent (e.g., a secure data destination).

The reports you can choose from include:

User Engagement
Goal Improvement
Feature Use
Member Reports
Roleplay Goals Reports
Roleplay Attempts

The destinations you can send to are:

Email
S3
GCS
Azure Blob Storage

How to set up Scheduled Reports

Go to Analytics
Go to Reports Tab
Click the Calendar icon next to any report to begin setting up the scheduled report
1. You have 3 reports to choose from, Member, Groups, and Roleplay Performance
2. Member Reports are User Engagement, Goal Improvement, Feature Use
3. Group Reports are the same but you will choose which groups are exported.
Choose where to export

Depending on where you export you will need the following information:

S3
- S3 supports two approaches for data export: Access Key/Secret Key based access, or providing Yoodli's service account access to your buckets
  - Access Key/Secret Key is simplest. Create a user with access to your bucket (no console access is required) and provide Yoodli with the following information
    Access Key ID
    Secret Access Key
    Region
    Bucket Name
    Object Key Prefix
  - Using Yoodli's service account
    For organizations that require no access keys to be used, you can grant Yoodli’s AWS bucket writer permission to write to your bucket instead. This uses AWS’ AssumeRole functionality to grant Yoodli’s AWS bucket writer the permissions to write to your bucket. To set this up
    Create a IAM user, which Yoodli's account will assume. The role should have permissions similar to the following
    {
    "Version": "2012-10-17",
    "Statement": [
    {
    "Effect": "Allow",
    "Action": [
    "s3:PutObject",
    ],
    "Resource": "arn:aws:s3:::customer-bucket-name/*"
    },
    }
    ]
    }
    You also need to create a Role Policy to allow the Yoodli bucket writer to assume your IAM user. sts-external-id is a secret passphrase that you will give to Yoodli to allow only our writer to assume your IAM user role.
    {
    "Version": "2012-10-17",
    "Statement": [
    {
    "Effect": "Allow",
    "Principal": {
    "AWS": "arn:aws:iam::850995565764:user/yoodli-bucket-writer-prod"
    },
    "Action": "sts:AssumeRole",
    "Condition": {
    "StringEquals": {
    "sts:ExternalId": "sts-external-id"
    }
    }
    }
    ]
    }
    On our reports page role, you will need to give us the following information: the ARN of the IAM user to assume and the external ID acting as the secret passphrase
Email
- Email Address
GCS
- Upload JSON credentials file (This can be obtained in the Google Cloud web console by navigating to the IAM page and clicking on Service Accounts in the left sidebar. Then, find your service account in the list, go to its Keys tab, and click Add Key. Finally, click on Create new key and choose JSON.)
- Bucket Name
- Object Prefix
Azure Blob Storage
- Storage Account Name
- Container Name
- Tenant ID
- Client ID
- Client Secret

Once you have completed this form click, "Save". You will be sent a report initially as a test to verify all the information is correct. Check your destination for this report. You will be notified of an error if a report has not been sent.

Still need help?

Contact [email protected] or click the messenger at the bottom right to chat