# Reviewing Real Time Triggered Activation Logs

This is the title of the webpage!

When a parent segment is enabled for real-time journeys and real-time trigger activations, Treasure Data automatically creates the following objects:

* **Database** : `cdp_audience_<_parent_segment_id_>_rt`
* **Table** : `activations`


These objects gather information to create an activation log. You can use the activation log to track information about your activations, such as:

* Failures
* Successes
* Journeys and their associated activations
* Profiles being activated
* The number of profiles activated


This topic includes:

* [Creating Your Query](#creating-your-query)
* [Example Queries](#example-queries)
* [Expected Results](#expected-results)


## Creating Your Query

Treasure Data suggests that you use the Presto engine for your query. Additionally, Presto has a Time Range functionality that can help you filter the query result.

1. Open TD Console.
2. Navigate to **Data Workbench**.
3. Select **Queries**.
4. Select **New Query**.
5. Enter your query.
6. Select **Run**.
7. Select **Query Result**.


### Example Queries

Query Using TD_TIME_RANGE With Timestamps


```sql
SELECT response, status, delivered, event_id, profile_id, activation_type, activation_id, activation_name, journey_name, timestamp from activations where TD_TIME_RANGE(time, 1716256019, 1716278847 )
```

#### Query Using TD_INTERVAL


```sql
SELECT response, status, delivered, event_id, profile_id, activation_type, activation_id, activation_name, journey_name, timestamp from activations where TD_INTERVAL(time, '-3d/now')
```

#### Query Using TD_TIME_RANGE With Specified Time Period


```sql
SELECT * from activations where TD_TIME_RANGE(time, '-12h')
```

![](/assets/reviewing-real-time-triggered-activation-logs-2024-05-22.97ea7b4a141bb698bba45c1c5be14fd63a282bd2e2cf4cfd3ea9f9784b135b55.cf3845cb.png)

## Expected Results

The following columns might be populated based on the query request and the values available:

* error
* response
* status
* delivered
* event_id
* profile_id
* activation_type
* activation_id
* activation_name
* journey_name
* timestamp


Fields are populated based on the event returned. For example, the *profile_id* is populated if the event contains *td_client_id; otherwise* , it will be null. Additionally, if there are no activation triggers for any of the following profile values:

* activation_type
* activation_id
* activation_name
* journey_name
* timestamp


the values will be null.