# Quickstart to Impact-Oriented Strategy

Understand the DoubleLoop method and platform in 30 minutes

## 1. The Feature Factory Problem

{% embed url="<https://www.loom.com/share/af664c9a82d64e03aff72101687e878a>" %}
5 minutes
{% endembed %}

Dig deeper:

* [Feature Factories vs. Value Generators](https://itamargilad.com/feature-factory/)
* [12 Signs You're Working in a Feature Factory](https://medium.com/@johnpcutler/12-signs-youre-working-in-a-feature-factory-44a5b938d6a2)
* [Why business intelligence falls flat](https://blog.doubleloop.app/why-dashboards-fall-flat/)

## 2. The DoubleLoop Method for Impact-Oriented Strategy

{% embed url="<https://www.loom.com/share/bc86410138c34593ab41a484cf2669a4>" %}
8 minutes
{% endembed %}

Dig deeper:

* [The DoubleLoop Method](https://doubleloop.app/method)
* [DoubleLoop templates and examples](https://doubleloop.app/method)
* [OKRs ≠ Strategy](https://blog.doubleloop.app/okrs-strategy/) (DoubleLoop blog)
* [The deep value of the North Star Framework is not a North Star metric](https://blog.doubleloop.app/the-deep-value-of-the-north-star-framework-is-not-a-north-star-metric/) (DoubleLoop blog)
* [North Star Playbook](https://amplitude.com/books/north-star) (Amplitude)
* [Don’t Become a Victim of One Key Metric](/measure/dedicated-outbound-ips) (Casey Winters)
* [Designing and Building Metric Trees](https://www.youtube.com/watch?v=Dbr8jmtfZ7Q) (Abhi Sivasailam)
* [KPI Trees: How to Bridge the Gap Between Customer Behavior, Product Metrics, and Company Goals](https://www.petra-wille.com/blog/kpi-trees-how-to-bridge-the-gap-between-customer-behavior-product-metrics-and-company-goals) (Petra Wille & Shaun Russell)
* [Growth Loops](https://www.reforge.com/blog/growth-loops) (Reforge)

## 3. Intro to the DoubleLoop Platform for Strategy Development

{% embed url="<https://www.loom.com/share/6b2632df00df4292832b58e8fed5af79>" %}
4 minutes
{% endembed %}

Dig deeper:

* [DoubleLoop features](https://doubleloop.app/features)

## 4. Creating Aligned Autonomy in Jira

{% embed url="<https://www.loom.com/share/fc3316bf40944d0f8bafb40c8683be82>" %}
2 minutes
{% endembed %}

Dig deeper:

* [Aligned autonomy](https://peerspectivegmbh.medium.com/aligned-autonomy-what-is-it-and-how-may-i-adopt-it-a4f8775371d9)

## 5. Using Correlation Scores to Optimize Strategy

{% embed url="<https://www.loom.com/share/1a620e8ea24248bfa4d124396b6585b0>" %}
5 minutes
{% endembed %}

Dig deeper:

* [Strategy, Systems Thinking, and Being Wrong](https://blog.doubleloop.app/strategy-systems-thinking-and-being-wrong/) (DoubleLoop blog)
* [How to do linear regression and correlation analysis](https://www.lennysnewsletter.com/p/linear-regression-and-correlation-analysis) (Olga Berezovsky on Lenny's Newsletter)
* [Pearson correlation coefficient](https://en.wikipedia.org/wiki/Pearson_correlation_coefficient) (Wikipedia)

## 6. Communicating Strategy at Different Altitudes

{% embed url="<https://www.loom.com/share/d00a171e011d49ac86bf7ceed8d2e318>" %}
2 minutes
{% endembed %}

## 7. Understanding The Impact of Bets

{% embed url="<https://www.loom.com/share/54ef8fbd2e5e46c4b059d100265f71f0>" %}
4 minutes
{% endembed %}

Dig deeper:

* [Continuous Roadmapping](https://cutlefish.substack.com/p/tbm-2152-continuous-roadmapping) (John Cutler)


# Roles

An overview of the account roles available in DoubleLoop

<table><thead><tr><th width="311"></th><th data-type="checkbox">Viewer</th><th data-type="checkbox">Editor</th><th data-type="checkbox">Admin</th></tr></thead><tbody><tr><td>View maps, metrics, and cards</td><td>true</td><td>true</td><td>true</td></tr><tr><td>Comment on map items</td><td>true</td><td>true</td><td>true</td></tr><tr><td>Add items to favorites</td><td>true</td><td>true</td><td>true</td></tr><tr><td>Edit maps, metrics, and cards</td><td>false</td><td>true</td><td>true</td></tr><tr><td>Add new maps, metrics, and cards</td><td>false</td><td>true</td><td>true</td></tr><tr><td>Manage card types</td><td>false</td><td>true</td><td>true</td></tr><tr><td>Invite new users</td><td>false</td><td>true</td><td>true</td></tr><tr><td>Manage existing users</td><td>false</td><td>true</td><td>true</td></tr><tr><td>Manage organization details</td><td>false</td><td>true</td><td>true</td></tr><tr><td>Manage billing</td><td>false</td><td>false</td><td>true</td></tr><tr><td>Manage Integrations</td><td>false</td><td>false</td><td>true</td></tr></tbody></table>


# Build your First Proof-of-Concept

Learn how to run a simulation of bet impact in 30-minutes.

Our approach is designed to help you get large benefits from Value Architecture, fast by using a deterministic KPI tree to run a simulation of bet impact.

1. **Build a deterministic KPI tree for your product/company.** To make this easier, start with one of these templates:
   1. [SaaS template](https://app.doubleloop.app/playbooks/saas-simulator-playbook)
   2. [eCommerce template](https://app.doubleloop.app/playbooks/ecommerce-simulator-playbook)
   3. [Generic template](https://app.doubleloop.app/playbooks/generic-simulator-playbook)
2. **Map a few bets/projects to inputs in your KPI tree**. The playbooks have examples. Replace those examples with real ones.
3. **Run a simulation** with a few colleagues.
   1. Enter simulation mode.
   2. Update your baseline values. It's OK to guess to get start quickly and refine your baselines later.
   3. Adjust your impact percentages.
   4. Click "Run sim"
   5. Compare the impact of your bets.

If you get stuck or would like feedback, reach out!

<figure><img src="https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2FAhSEsneVDMOVkv3Ohtjk%2FCleanShot%202025-02-26%20at%2015.48.20%402x.png?alt=media&amp;token=36e6eea6-d690-434f-8a12-74557fb07fb9" alt=""><figcaption><p>Example eCommerce Simulation<br></p></figcaption></figure>

<figure><img src="https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2FvEqQMApNauh2VTFLCUMc%2Fimage.png?alt=media&amp;token=a8f00c32-a7b1-4c61-8b7e-33b1ed6231a5" alt=""><figcaption><p>Example SaaS Simulation</p></figcaption></figure>


# Map objects

This page describes how to use the different types of objects you can add to maps.

<figure><img src="https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2FvO22D91lTEXK48vwi2PP%2FCleanShot%202024-01-23%20at%2022.33.13%402x.png?alt=media&amp;token=23af780d-55e1-4eb2-9d31-1e9a465687f8" alt=""><figcaption></figcaption></figure>

## Cards (a.k.a. Flexible cards)

Use "Cards" to add any type of object you'd like to maps. You can customize the "types" of cards you add to match the vocabulary of your company.

Examples: Objectives, Customer Journey Steps, Pillars, Teams.

## Metrics

"Metrics" have time series data aggregated into stats. You can connect metrics to your data sources. Connect two metrics to see the correlation between them. You can attach key results to metrics if you'd like to set targets.

Examples: Monthly active users, ARR.

## Bets

"Bets" can be anything your company is investing in to achieve a business outcome. You can record hypotheses and results for bets.\
\
Examples: Improve song recommendation algorithm, launch new marketing campaign.

## Work

"Work" is similar to bets, but it's more intended for tactical execution. If you connect your work management tool, you can add (e.g.) Jira objects directly to your maps.

Examples: Implement AI model for song recommendations, back-end refactor.

## Sub-maps

If your map is getting too complex, you can nest maps inside maps. For example, you might have a company-wide map that shows how your products fit into the big picture of your strategy. Each product itself can be a map, with its on metrics.

Example: Marketing strategy, Checkout team strategy

## Sections

Use sections to logically organize your map. Add connectors to sections to avoid having to draw lots of connects to individual nodes.

## Notes

Add any text you want to provide context.

## Images

Add screenshots or any image you'd like.


# How to add metric data

Learn how to get your metric data into DoubleLoop

By adding your metric data into DoubleLoop, you can see stats on your strategy map and metrics graphs for your workstreams.

## Import data from your analytics tools

DoubleLoop allows you to import time series data from your analytics tools like Snowflake, Redshift, Postgres, and Looker. See our full list of [integrations](https://doubleloop.app/integrations).

To connect a metric to a data source, follow these steps:

1. Double-click a metric on your strategy map or click the "i" icon for a metric.
2. Click on the "Source" tab in the right drawer.
3. Follow the steps to connect the source.

Reach out to us if you have questions! This gif illustrates:

<figure><img src="https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2FObbr0aXwTFZ9y04VPZ1T%2FCleanShot%202022-12-01%20at%2022.12.07.gif?alt=media&amp;token=d6c71bad-5cbc-4a91-a5db-0acca6d070a4" alt=""><figcaption></figcaption></figure>

## CSV upload

Learn about it [here](/measure/upload-metrics-via-a-csv-file).

## Add random dummy data!

Before you connect your metrics in DoubleLoop to data sources, you can populate your map with random dummy data so you can see and share what a data-integrated map will look like.

Here's a demo:

{% embed url="<https://www.loom.com/share/54ab3e6ba1d640878fcacddf16ec6d8a>" %}

## Add data points manually

Sometimes it's easiest to enter data by hand. Here's how to do it:

1. Click on a metric in the strategy map or from the metric page.
2. Click "Create data point."
3. Enter the value and date.
4. Click "Save."

## Metrics API

Check out our [Metrics API](https://app.doubleloop.app/apidocs/1.0/metrics.html) doc.

##


# Metric types

DoubleLoop's tool for mapping your strategy was inspired by Amplitude's [North Star Playbook](https://amplitude.com/north-star) by John Cutler and Jason Scherschligt. The framework provides a model for how work and metrics relate to each other:

![Adapted from Amplitude's North Star Playbook](https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2Fgit-blob-614593869ad6bc54a890704b1ae267d9660cecfc%2Fimage.png?alt=media)

There are three types of metrics in DoubleLoop that live on a spectrum from leading to lagging indicators:

* **Input metrics**. Input metrics are *leading indicators* that can be influenced by work, like the percent of users that perform a certain action during a session. By themselves, they don’t equate business success.
* **North Star metric**. Your North Star metric is how you measure the value you're delivering customers. If you grow the metric, you'll make your users and happy and grow your business. It's the bridge between your leading and lagging indicators. A rule of thumb is that you should have one North Star metric per product at your company.
* **Business KPIs**. Business KPIs are lagging indicators that matter for your business; things like revenue and customer retention. Because they are lagging and subject to external forces, they often can't be impacted directly by work.

For background on how the top companies think about their metrics, see our post, [*Metrics-driven product development is hard*](https://blog.doubleloop.app/metrics-driven-product-development-is-hard/).


# Control the stats on your strategy map

Learn how to control what stats appear on your strategy map

In this doc, you'll learn how to control the stats that appear on your strategy map. You can control the time intervals, the roll-up calculations, and the format.

![](https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2F4fpXL1nyt2Z2bhuLUUet%2FCleanShot%202022-06-12%20at%2020.20.57%402x.png?alt=media\&token=09028b97-7453-4eb2-9916-ec03141ac1fe)

## Control the time intervals

By default, stats on your strategy map will display with the time intervals Past 7 days, Past 6 weeks, and past 12 months. You can change these intervals to whatever is right for your business.

To change the time intervals, go to the full metric settings page and adjust these settings:

![](https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2FEmamxGEdFCHCqqnTwqgu%2FCleanShot%202022-06-12%20at%2020.27.50%402x.png?alt=media\&token=fc0d64f1-ebf9-476e-921b-307a9c78a320)

## Control the roll-up calculations

![](https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2F2OcpXyBvU2HAqcRG032h%2FCleanShot%202022-06-12%20at%2020.32.54%402x.png?alt=media\&token=892d1851-b85a-415a-920e-dd9b04d6afad)

Choosing the right roll-up calculation depends on the nature of the metric. Here's how each roll-up calculation works, and when to use it.

| Roll-up calculation                                                                   | How it works                                                                                                                                     | When to use it                                                                                              |
| ------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------- |
| Sum                                                                                   | Sums the metric values for each time interval.                                                                                                   | Good for metrics that capture the amount of something on each day or month.                                 |
| Average                                                                               | Averages the metric values for each time interval.                                                                                               | Good for metrics that can't be summed, like "Daily active users" or percentages.                            |
| Amount increased                                                                      | Subtracts the value at the beginning of the interval from the value at the end of the interval.                                                  | Good for metrics that represent a cumulative total, like the total number of total subscribers on each day. |
| [Weighted average](/measure/control-the-stats-on-your-strategy-map/weighted-averages) | <p>Only works for metrics with a source of "calcuations."<br><br>Divides the sum of the numerator values by the sum of the dominator values.</p> | Good for metrics like conversion rates when a simple average is misleading.                                 |

## Change percentages

![](https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2FNTZALiWZubWaeCkSXiTQ%2FCleanShot%202022-06-12%20at%2020.59.51%402x.png?alt=media\&token=d199e69e-5903-4f56-bb16-b87a1c11c389)

The percentages that appear beneath each metric stat show how the metric performed compared to the previous period of the same length.

For example, if the roll-up value for the metric is 5 in the last seven days and was 4 in the seven days prior, the change percentage would be 25%.

Here's how the percent change calculation always works:

**(current period - previous period) / (previous period)**

## Format

![](https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2FhKFSIPJBc2VXnYLKzvjI%2FCleanShot%202022-06-12%20at%2020.56.29%402x.png?alt=media\&token=f18bf117-4f73-42b4-afba-c1e92f59b9b5)

The format only controls what symbol appears along with the metric value. E.g., for a metric like "Revenue," use one of the currency formats.


# Weighted averages

When a simple average won't suffice.

For a metric like conversion rate, a simple average over multiple days provides a misleading picture. For example, activity on the weekends is often much different than the weekdays.\
\
Here's how to do weighted averages in DoubleLoop so you can get an accurate sense of metric performance over time.

1. Instead of sending a metric like conversion rate to DoubleLoop, send the numerator and the denominator as separate metrics. For example, create two separate metrics for transactions and sessions.
2. Create a metric source in DoubleLoop I set "Calculated" as the source. This will allow you to select the numerator and denominator.
3. Attach a metric to your calculated metric source.
4. For the roll-up calculation for the metric, choose "Weighted average." When this option is selected, the map stats will divide the sum of the numerator values by the sum of the denominator values.

![Creating a metric source where you can specify the numerator and denominator](https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2FigJuNVgjTWWJyzJNKw0L%2FCleanShot%202022-06-12%20at%2022.39.03%402x.png?alt=media\&token=9ff74fce-4c6a-4c5b-bfe3-d6b0bb169d6c)


# Google Sheets integration

Learn how to use Google Sheets to populate you maps with data

Our Google Sheets integration is a good way to quickly populate your stategy maps with  data, without deeper data integrations. Even if you're planning to ultimately connect DoubleLoop directly to your metric sources for automation, the Google Sheets integration can be a great way to make a proof-of-concept of a data-connected maps.

## Video overview

This video provides a high-level overview of how the Google Sheets integration works:

{% embed url="<https://www.loom.com/share/ffdfa3b97e074ce98a0a6fca983cb3bc>" %}

## Example

Here's an example of a Google Sheet populated with data that you can import into DoubleLoop:

<https://docs.google.com/spreadsheets/d/16a0fuGdG_2oCr4H0mzjM1BMnBkiOkeuE-hSEOBZmt9o/edit#gid=0>

## Connecting Google Sheets to DoubleLoop

1. Go the [Metrics listing page](https://app.doubleloop.app/metrics).
2. Click the "..." in the upper right and click "Connect to Google Sheets"
3. Follow the authorization steps.
4. Click the "..." and click "Open Linked Data sheets"

## Importing data from Google Sheets into DoubleLoop

1. The top of your linked Google Sheet has detailed instructions for how to use the integration (see example above).
2. After you've updated data in your Google Sheet, you can import the data into DoubleLoop by clicking "Import latest data" on the [Metrics listing page](https://app.doubleloop.app/metrics).&#x20;

Notes:

* You can use the Google Sheet integration to update existing metrics in DoubleLoop or add new metrics. See the instructions at the top of the linked Google Sheet. To add a metric to the map that you added via Google Sheets, after clicking the "Metric" option on a map, you can search to find that metric.
* The Google Sheets integration is not a bi-directional sync. If you make changes in DoubleLoop and would like the Google Sheet to reflect that, you can unlink your linked Google Sheet and re-connect. This will export the latest data to a linked Google Sheet.


# Amazon Redshift integration

Learn how to populate metrics in DoubleLoop via Amazon Redshift.

DoubleLoop allows you to populate your metrics in DoubleLoop with time-series data from Redshift. Here's how to do it.

1. Get your Amazon Redshift Host, Port, Database Name, Username, and Password ready, or ask your IT team for assistance in getting this information for your Amazon Redshift instance.

   <mark style="color:red;">**Important**</mark><mark style="color:red;">: You will need to make sure the Amazon Redshift instance is reachable over the internet.</mark>
2. In DoubleLoop, double-click on a metric on the map.
3. Click the "Source" tab in the right drawer.
4. Choose "Amazon Redshift" as the source.
5. Fill in your Host with either the domain name or IP address of your Amazon Redshift instance.
6. Fill in the Port with your port, the default for Amazon Redshift is 5439.
7. Fill in your Amazon Redshift database name, username, and password.
8. Input the query into DoubleLoop. The output of the query must contain columns named "date" and "value". We recommend that you test out the query in Redshift before you input it into DoubleLoop.
9. Click "Save".

If you get stuck, please reach out!

<figure><img src="https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2FVkRXmEaIRbGxvXSjEoaK%2Fimage.png?alt=media&amp;token=17edf11f-6c60-4366-b66c-f419a4081c5d" alt=""><figcaption></figcaption></figure>


# BigQuery integration

Learn how to populate metrics in DoubleLoop via BigQuery.

DoubleLoop allows you to populate your metrics in DoubleLoop with time-series data from BigQuery. Here's how to do it.

### BigQuery Permissions

See [Google's documentation](https://cloud.google.com/iam/docs/service-accounts-create) for information on how to setup a service account and download your credentials file.

#### High-level Permissions

Use the following permissions to quickly get started.

*BigQuery Data Viewer, BigQuery Job User*

#### Granular Permissions

If you prefer more granular permissions, these are the specific required permissions.

*bigquery.jobs.create, bigquery.datasets.get, bigquery.tables.getData, bigquery.tables.list*

### Setup in DoubleLoop

1. In DoubleLoop, select on a metric on the map.
2. Click the "Source" option in the toolbar.
3. In the Source menu in the right side drawer, click "Add Source."
4. Select Google Big Query and click Next.
5. Upload the credentials file from above and follow the steps.
6. Input the query into DoubleLoop for the metric. The output of the query must contain columns named "date" and "value". We recommend that you test out the query in BigQuery before you input it into DoubleLoop.
   * To import segmented data, see the data format [here](/measure/data-segmentation).
7. Click "Save".
8. You can import data immediately by clicking "Run now". Moving forward, the data will import on daily basis.

If you get stuck, please reach out!


# CSV file upload

Learn how to upload metric data into DoubleLoop with CSV files.

Our CSV upload tool is a great way to get a lot of metric data into DoubleLoop without integrating your tools or using our API.

There are two ways to use CSV upload in DoubleLoop:

* Upload data points for an individual metric.
* Upload data points for many metrics at once.

## Upload data points for an individual metric

#### **1. Prepare your CSV file.**

Download an example file here:

{% file src="/files/TqFnUfy4OBBDiSy3pBQE" %}

The file looks like this:

![](https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2Fgit-blob-3f79a3c65351fd138c8712340b8cbad34e905c04%2FCleanShot%202022-03-25%20at%2017.15.05%402x.png?alt=media)

Or like this if you open it in Excel:

![](https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2Fgit-blob-cecfc904d5f24f712b5c66db5cbb1dfebba27552%2FCleanShot%202022-03-25%20at%2017.09.55%402x.png?alt=media)

Replace the dates and values with the data you'd like to upload and save the file.

<mark style="color:green;">**Some important notes:**</mark>

1. <mark style="color:green;">**Use the date format yyyy-mm-dd**</mark>
2. <mark style="color:green;">**Make sure you leave "date" and "value" as the headers.**</mark>

**2. Go to the individual metric in DoubleLoop.**

You can navigate to the metric either from your strategy map or the metric listings page.

#### 3. Click "Upload CSV."

![](https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2Fgit-blob-36cbcfc3a74baf012a42a641ef965b696f19bb10%2FCleanShot%202022-03-25%20at%2017.20.40%402x.png?alt=media)

#### 4. Upload the file.

After you upload the file, you'll need to refresh the page to see the data you uploaded.

## Upload data points for many metrics at once

#### **1. Prepare your CSV file.**

Download an example file here:

{% file src="/files/mPAwxxvxuyS6JcL992aw" %}

The file looks like this:

![](https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2Fgit-blob-1107d356b3c1676241bf38db8e4dd47dfe9b8ca5%2FCleanShot%202022-05-25%20at%2015.56.58%402x.png?alt=media)

Or like this if you open it in Excel:

![](https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2Fgit-blob-97271c8aefa2d8a633616594a0b62b6636bb91a6%2FCleanShot%202022-05-25%20at%2016.00.02%402x.png?alt=media)

Each row contains a metric id, date, and value. You can find the metric id on the metric page under the metric name, as shown here.

![](https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2Fgit-blob-c09285727813675232ffd2e3e1aff1bba42f6c1e%2FCleanShot%202022-05-25%20at%2016.02.34%402x.png?alt=media)

<mark style="color:green;">**Some important notes:**</mark>

1. <mark style="color:green;">**Use the date format yyyy-mm-dd**</mark>
2. <mark style="color:green;">**Make sure you leave "id", "date", and "value" as the headers.**</mark>

**2. Go to the metric listing page in DoubleLoop.**

Click "Metrics" in the left nav or go here: <https://app.doubleloop.app/metrics>

#### 3. Click "Upload CSV."

![](https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2Fgit-blob-7276883fbda63561a64085353a4b74c916c2b104%2FCleanShot%202022-05-25%20at%2016.06.16%402x.png?alt=media)

#### 4. Upload the file.

After you update the file, you'll need to refresh the metrics page to see that data you uploaded.

That's it! If you have any questions, problems, or improvement ideas, let us know.


# Google Analytics integration

Learn how to populate metrics in DoubleLoop from Google Analytics.

DoubleLoop allows you to populate your metrics in DoubleLoop with time-series data from Google Analytics. Here's how to do it.

1. Make sure your Google Analytics user has **Analyst**, **Editor**, or **Administrator** permissions in **Google Analytics**.
2. Go to the [DoubleLoop Google Analytics Integrations page](https://app.doubleloop.app/settings/integrations/google), click connect, and authorize with Google.
3. In DoubleLoop, double-click on a metric on the map.
4. Click the "Source" tab in the right drawer.
5. Choose "Google Analytics" as the source.
6. Specify the property, metric, and segment you'd like to import into DoubleLoop.
7. Click "save."

If you get stuck, please reach out!

![](https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2F2XywkH0yA0t5Y6Nlt6d3%2Fimage.png?alt=media\&token=1a013e01-e9f3-4eee-98da-6f03bf330368)


# Looker Action Hub integration

Import your KPIs or metrics into DoubleLoop to see actions and outcomes in one place. It's the best way to align a team around an initiative.

<mark style="color:red;">**Important**</mark><mark style="color:red;">: If your Looker instance is configured for IP based security, our outbound IP addresses are 35.160.120.126, 44.233.151.27, and 34.211.200.85. We use Look data downloads to allow for large data sets and require access to fetch the download.</mark>

## How to enable Looker integration

**Important note**: to turn on Looker integration, you may need to be a Looker admin.

1. If you haven't already, [create your DoubleLoop account](https://app.doubleloop.app/sign_up).
2. In Looker, go to the "Actions" screen in the admin section.

   <img src="https://lh5.googleusercontent.com/WbhzV8d10brLouNCrNZnMh_YNl34wYTSMcyFc6Y0PHTlpWESXrtbfXMiD8w09aSoOPevPsOajhKTo8UAAxX_wCw-Vec59Ej-AH8yX6asVnxhWqMk2yj0DA7GqtqQn115L66uobUX" alt="" data-size="original">
3. Click `Add Action Hub`.
4. Add the Action Hub Url: `https://app.doubleloop.app/looker`
5. Click the `Enable` button on the Track Metric action. This will bring up the Action configuration. Grab your API key from the DoubleLoop [Integrations](https://app.doubleloop.app/settings/integrations) page or from any newly created Metric Looker Data Source and paste it into the API Key box. Make sure to toggle the `Enabled` slider and click `Save`.

   <img src="https://lh4.googleusercontent.com/puEdxX1fDJRlfZFP_UxkS4gqn3ZagXMCh4Gxy2yEZGLWeoMJEst3JfZ_df-O8v2JkVWnSnECVBWkFvO6bzbDW3WWEmX7eD1XddFScmVvE7afKBB9nsrsJj_mwi2VgfuEQ5jTb3Ch" alt="" data-size="original">

## How to send metrics from Looker to DoubleLoop

1. Create a Metric in DoubleLoop and add a Looker Data Source. This can either be done from the [metrics list](https://app.doubleloop.app/metrics) or via the strategy maps by clicking `+ Metric`, clicking the (i) icon on the newly created metric, and switching to the `Source` tab.\
   ![](https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2FFZ1o6SSXe8MuaYaIJNW7%2Fstaging.doubleloop.app_strategy_885\(Desktop\)%20\(1\).png?alt=media\&token=8130fbd6-1413-496f-bb50-fab74c628a0e)
2. Fill in the Date field and Value field boxes, they should match the **bold** part of the table column name in the Looker Looks data table. In the example below, you would use `date date`  and `created`. \
   \
   *If you have any issues here, continue following the instructions below and let us know when you're finished, we'll be glad to help you figure out what values to use.*\ <img src="https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2FwcJe5P5unASqDR10i5PM%2FScreen%20Shot%202022-08-18%20at%209.54.16%20AM.png?alt=media&amp;token=7ee0b8b6-9c20-4940-aaff-7a8ba4cb5a5d" alt="" data-size="original">
3. Find the Looker Look that contains the metrics you’d like to provide to DoubleLoop. \ <mark style="background-color:yellow;">**The Look must contain at least one date field and one value field.**</mark>
4. From the Look configuration menu, choose the \`Schedule...\` option.

   <img src="https://lh4.googleusercontent.com/c0vBVEigZRLQ3ld-WJj2ZRL6m0K6zGEiAGrJtkeaoJeGZU08vndfw3pfxyCFA_rq4QDkCd7GSO5mwcpWFXDRDB54Rvc8ZFGN2PXxqWRwI07mQ-QcBTRPKoTDS9daSNDWyUqpTGYL" alt="" data-size="original">
5. Give your Schedule a memorable name, choose the DoubleLoop metric you'd like to receive data from the `DoubleLoop Metric Source` dropdown, and pick how often you’d like it to send (we suggest daily). Hit `Send Test` followed by `Save All`. \
   \
   *Optionally, if you'd like to control the number of records sent to DoubleLoop, expand the Advanced options section.*

   <img src="https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2FE0h7GWnw6iC6VccaJeTg%2FScreen%20Shot%202022-08-18%20at%209.23.52%20AM.png?alt=media&amp;token=4dd29ffd-77e2-4f16-a4d9-ab72f99668d9" alt="" data-size="original">\
   \ <mark style="background-color:yellow;">**Looker restricts the number of records a Look can send. If you go over the Look limit, you will need to limit the Look itself, outside of the schedule's filter options.**</mark>&#x20;
6. To see your Looker data in DoubleLoop, either visit the [metrics list](https://app.doubleloop.app/metrics) and pick the metric you chose in the Look Schedule window or find it on your strategy map and double-click on the metric or click the (i) icon.\
   ![](https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2F5u5H35SewY09MUZQMi8V%2Fstaging.doubleloop.app_strategy_885\(Desktop\).png?alt=media\&token=3238d534-25ae-4b96-8073-3cdfa168f6b2)
7. If you need to update your Looker configuration in DoubleLoop, click on the `Data Source` tab and make any necessary edits.


# Looker API integration

Import your KPIs or metrics into DoubleLoop to see actions and outcomes in one place. It's the best way to align a team around an initiative.

## How to setup the Looker API Key

**Important note**: to setup the Looker integration, you may need to be a Looker admin.

1. If you haven't already, [create your DoubleLoop account](https://app.doubleloop.app/sign_up).
2. In Looker, go to the "Users" screen in the admin section.

   ![](https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2F9nCEZ9LCiveO8HDZPueM%2Fdoubleloop.cloud.looker.com_admin_next_users%20\(1\).png?alt=media\&token=93d2e088-36f3-42b5-9127-eea1be5217d0)
3. Choose or create a User that you'd like to give API access. We recommend creating a user specifically for DoubleLoop. Once you've chosen, click on that User.
4. On the User page, click the `Edit Keys` button next to the API Keys label which will open the users API Key manager.\
   ![](https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2FeBZ8PLmTqigtqMtiaD9s%2Fdoubleloop.cloud.looker.com_admin_users_api3_key_4.png?alt=media\&token=fd7f6a8f-98cf-4e4c-9b59-5aa68d958a19)
5. Add a new API Key and make note of the Client ID and Client Secret as we will need those to configure the Integration in DoubleLoop.
6. This is also a great time to grab the Looker API Host URL we'll need as well if you don't know if already. It can be find in the Looker Admin area under `Platform -> API`.\
   ![](https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2FeJiWZD2RUf3REINRDsvy%2Fdoubleloop.cloud.looker.com_admin_api%20\(1\).png?alt=media\&token=5803e1f6-6a19-4a3c-a51c-7cafcd844c47)

## Setting up the DoubleLoop Integration

1. Go to the [DoubleLoop Integrations Page](https://app.doubleloop.app/settings/integrations) and click `+ Add Integration`.\
   ![](https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2FviPQoykEZW677lYiwf8L%2Fapp.doubleloop.app_settings_integrations.png?alt=media\&token=5f3d8580-99ab-4f04-be9b-7621e8b18084)
2. In the popover choose Looker API and hit `Next`.&#x20;
3. Fill in the details in the popover, we suggest giving your integration an easy to remember name to help keep track of the integration.
4. In the API endpoint field, use the Looker API Host URL mentioned above making sure to add `/api/4.0` on the end to match the placeholder text.
5. Finally, use the `Test credentials` button to test that it's all setup correctly and hit `Save` to finish setting up the integration.

## How to configure a metric with the Looker API Integration

1. Create a Metric in DoubleLoop and click on the `Source` tab.
2. Click on the Source dropdown and choose the Integration we created above.![](https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2FNUea13LuxKandZyXmSw2%2Fapp.doubleloop.app_settings_integrations%20\(1\).png?alt=media\&token=c41d1415-4246-472b-9a02-5481cde88a8e)<br>
3. Select your Look, which will then fetch the fields from that Look and show a list of available fields for the Date and Value for DoubleLoop to parse. Optionally, pick an Import time if the default does not work for you. \
   ![](https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2Fo9OGMEtx6DOyFOpyydJu%2Fapp.doubleloop.app_settings_integrations%20\(2\).png?alt=media\&token=8bd76cd3-2f91-43aa-ab03-63cca8b05f17)
4. Finally, save the changes. An automatic historical import will be started and new daily metric data should begin to flow into DoubleLoop.&#x20;
5. If you need to update your Looker configuration in DoubleLoop, click on the `Source` tab, then the `Edit` button, and finally make any necessary edits.


# Amplitude integration

Learn how to use DoubleLoop's amplitude integration

## Overview

DoubleLoop enables teams to align on their metrics-driven strategy. After populating your DoubleLoop map with live data from Amplitude, you can make sense of how your product metrics ladder up to your business objectives to analyze which of your initiatives are driving impact.

To get a general overview of DoubleLoop, see our [demo video](https://www.loom.com/share/395283236e414e89bfd0a5cbef0b51b3).

See below for our [future plans](#future-vision) for evolving this integration.

## Example DoubleLoop map with Amplitude data

<figure><img src="https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2Fs6JxIAkGxbZ79BMkdWeC%2FCleanShot%202024-05-05%20at%2015.25.23.png?alt=media&amp;token=0f1309e3-d7b6-47ec-8c57-1e931e1eead2" alt=""><figcaption></figcaption></figure>

## Instructions

### 1. Add Amplitude as a data source

1. After logging into your DoubleLoop account, go to the [integrations page](https://app.doubleloop.app/settings/integrations).
2. In the "Metrics" section, click "Add integration."
3. Select "Amplitude"
4. Enter your API key and Secret key. See [here](https://www.docs.developers.amplitude.com/analytics/find-api-credentials/) for where to find this info.
5. Click "Save.

Note: you can create multiple Amplitude sources in DoubleLoop for multiple Amplitude proejcts.

### 2. Populate your DoubleLoop metric with Amplitude data

{% embed url="<https://share.cleanshot.com/PTqSZqWX>" %}

1. On one of your strategy maps in DoubleLoop, select a metric.
2. In the toolbar, click "Data source"
3. In the source menu in the side drawer, select your Amplitude source.
4. Select a query type of "Event" or "Chart".
   * Note: "Chart" is recommended for more flexibility.
5. Complete the form by either selecting an event of entering a chart URL (like this one:`https://app.amplitude.com/analytics/doubleloop/chart/jkf5qy9b`
   * Note: DoubleLoop is only be able to import charts with time series data; dates and values.
6. Save changes.
7. Go to the "Data" tab in the side drawer for the metric to see the data that was imported from Amplitude.

Moving forward, DoubleLoop will import your metric data daily at a time of your choosing, or you can manually click "run now" to immediately update the data.

## Future vision

The current Amplitude integration makes it easy to pull in Amplitude metrics into DoubleLoop one metric at a time.

Our future vision for the integration is to seamlessly pull in Amplitude metrics en masse into DoubleLoop.

Examples:

* After connecting DoubleLoop to Amplitude, we could automatically populate your metric library in DoubleLoop with all of your charts.
* We could enable you to select an Amplitude funnel and automatically create a DoubleLoop map for your funnel, populated with data.
* We could enable you to select an Amplitude dashboard or notebook and automatically add all included metrics to your DoubleLoop map.


# Mixpanel integration

Learn how to populate metrics in DoubleLoop via Mixpanel

## Overview

DoubleLoop enables teams to align on their metrics-driven strategy. After populating your DoubleLoop map with live data from Mixpanel, you can make sense of how your product metrics ladder up to your business objectives to analyze which of your initiatives are driving impact.

To get a general overview of DoubleLoop, see our [demo video](https://www.loom.com/share/395283236e414e89bfd0a5cbef0b51b3).

## Instructions

### 1. Add Mixpanel as a metric source

1. After logging into your DoubleLoop account, go to the [integrations page](https://app.doubleloop.app/settings/integrations).
2. In the "Metrics" section, click "Add integration".
3. Select "Mixpanel"
4. Enter your project id and the username/password for your Mixpanel service account. See [here](https://docs.mixpanel.com/docs/orgs-and-projects/managing-projects#viewing-project-information) for information regarding your project id. See [here](https://developer.mixpanel.com/reference/service-accounts) for instructions on how to create a service account, make sure to grab the password as it's only available during creation.
5. Click Save

Note: you can create multiple Mixpanel sources in DoubleLoop for multiple Mixpanel projects.

### 2. Populate your DoubleLoop metric with Mixpanel data

1. On one of your strategy maps in DoubleLoop, select a metric.
2. In the toolbar, click "Data Source".
3. In the source menu in the side drawer, select your Mixpanel source.
4. Select an event type of "Event Data" or "Insights Report".
5. Complete the form by either filling in the event name or the URL of the insights report.
6. Make sure the region matches where your Mixpanel data is stored, US or EU.
7. Save changes.
8. Go to the "Data" tab in the side drawer for the metric to see the data that was imported from Mixpanel. Note: this might take a few minutes for larger data sets.

Moving forward, DoubleLoop will import your metric data daily at the time of your choosing, or you can manually click "run now" to kick off the data import process.


# MySQL

Learn how to populate metrics in DoubleLoop via MySQL

Docs coming soon. Check out our general instructions for connecting metrics to a data source [here](/measure/how-to-add-metric-data). Please reach out if you get stuck in the meantime.


# PostgreSQL

Learn how to populate metrics in DoubleLoop via PostgreSQL.

DoubleLoop allows you to populate your metrics in DoubleLoop with time-series data from PostgreSQL. Here's how to do it.

1. Get your PostgreSQL Host, Port, Database Name, Username, and Password ready, or ask your IT team for assistance in getting this information for your PostgreSQL instance.

   <mark style="color:red;">**Important**</mark><mark style="color:red;">: You will need to make sure the PostgreSQL instance is reachable over the internet.</mark>
2. In DoubleLoop, double-click on a metric on the map.
3. Click the "Source" tab in the right drawer.
4. Choose "PostgreSQL" as the source.
5. Fill in your Host with either the domain name or IP address of your PostgreSQL instance.
6. Fill in the Port with your port, the default for PostgreSQL is 5432.
7. Fill in your PostgreSQL database name, username, and password.
8. Input the query into DoubleLoop. The output of the query must contain columns named "date" and "value". We recommend that you test out the query in PostgreSQL before you input it into DoubleLoop.
9. Click "Save".

If you get stuck, please reach out!

![](https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2FkruULy19kM8qrOp1w7oe%2Fimage.png?alt=media\&token=88c42ea9-8f0c-4255-aa38-ff8100bb1bcd)


# Snowflake integration

Learn how to populate metrics in DoubleLoop via Snowflake.

DoubleLoop allows you to populate your metrics in DoubleLoop with time-series data from Snowflake. Here's how to do it.

1. Get your Snowflake **Host**, **Port**, **Warehouse name**, **Database name**, **Schema name**, **Username**, and **Password** ready, or ask your IT team for assistance in getting this information for your Snowflake instance. If your connection requires Snowflake roles, you'll need that as well. \
   \
   We recommend following [this guide](https://docs.snowflake.com/en/user-guide/security-access-control-configure) from Snowflake on how to setup a role.

   \ <mark style="color:red;">**Important**</mark><mark style="color:red;">: If your Snowflake instance is configured for IP based security, our outbound IP addresses are 35.160.120.126, 44.233.151.27, and 34.211.200.85.</mark>
2. In DoubleLoop, double-click on a metric on the map.
3. Click the "Source" tab in the right drawer.
4. Fill in your Host with either the domain name or IP address of your Snowflake instance **without the https\:// or the trailing slash**. You can use the bottom left menu on Snowflake to find your Host.\
   \
   ![](https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2Ffzbj3MUMhL0oSP8odrvt%2FScreenshot%202024-01-17%20at%203.43.10%E2%80%AFPM.png?alt=media\&token=a46aec69-004b-4373-809d-d0d5a89d124e)
5. Fill in the Port with your port, the default for Snowflake is 443.
6. Fill in your Snowflake warehouse name, database name, schema name, username, and password.
7. Input the query into DoubleLoop. The output of the query must contain columns named "date" and "value". We recommend that you test out the query in Snowflake before you input it into DoubleLoop.
8. Click "Save".

If you get stuck, please reach out!

![](https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2FxrKzAgOs2K8YB5BTYDel%2Fimage.png?alt=media\&token=d3bc11dc-96d5-4d3c-b83d-2e39360e5185)


# Dedicated outbound IPs

DoubleLoop uses a static set of outbound IPs for enhanced security.

## Usage

Using the dedicated outbound IPs is not required, however it will enhance the security of your Integrations with DoubleLoop.

* IT Documentation:
  * [PostgreSQL](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html)
  * [Redshift](https://docs.aws.amazon.com/redshift/latest/gsg/rs-gsg-authorize-cluster-access.html)
  * [Snowflake](https://docs.snowflake.com/en/user-guide/network-policies.html)
  * [Looker](https://cloud.google.com/looker/docs/admin-panel-server-ip-allowlist)
  * For other integrations, please contact us for assistance.

## IP List

35.160.120.126

44.233.151.27

34.211.200.85


# Data segmentation

This page describes how to setup data segmentation in DoubleLoop.

*Note: The data segmentation feature is available to subscribers of our "Scale" plan. If you'd like access, let us know.*

## What is data segmentation in DoubleLoop?

With data segmentation, you can tag the data points you import into DoubleLoop with one or more segments; e.g., geography, new/returning users, pricing plan, etc..

After you've uploaded segmented data, you can then filter a map by one or more segments. When you do so, the stats and correlation scores will update to reflect only data from your selected segments.

<figure><img src="https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2F4YBzmhTB4Opq4YP1XYRn%2FCleanShot%202024-01-24%20at%2023.19.04.gif?alt=media&amp;token=c4eb8a6e-685b-44a2-a9b1-0c5bd711ac49" alt=""><figcaption></figcaption></figure>

## Why is data segmentation useful?

Different user segments behave differently. E.g., your European users might be converting at a higher rate than your North American users. For European users, average order size might be highly correlated with revenue, but not for North American users. These are actionable insights that can influence your product strategy.

## How do you import segmented data?

The format for segmented data looks like the below. In the example, in row 2, the data point has two segments, user\_type:New and geograhy:North America.

You can have as many segments as you'd like.

<figure><img src="https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2FL9llaWmsHo57pzPDhnUJ%2FCleanShot%202024-01-24%20at%2023.28.05%402x.png?alt=media&amp;token=4434d17b-9fda-4fe7-9c16-0bcdaf2189ff" alt=""><figcaption></figcaption></figure>

### Import segmented data from your data warehouse

Go to the "Source" tab for a metric and select your source (e.g., Snowflake). Enter a query that returns data structured like above.

### Upload CSV files of segmented data

Go to the "data" tab for a metric and click Upload CSV. Here's en example file:

{% file src="/files/1kKq2wCDo92DADOZt8rE" %}

## How do you know if it worked?

You know that you've successfully uploaded segmented data if you see the option to filter by segment at the bottom of your map.

If you have any questions, let us know.


# Bulk Importing Bookmarklet

A quick overview on how to install and use the DoubleLoop Bulk Import bookmarklet.


# Jira app

Communicate the business context of work in Jira.

## A note to beta testers

Thanks so much for being one of the first to try out our new Jira app. We're excited for you feedback, bug reports, and enhancement ideas.

During this early phase of development, we will be rapidly iterating on the Jira app. Things are likely to change fast! If something looks broken, please let us know. We appreciate your patience.

Also, a headsup: early testers might be asked to uninstall and reinstall the app as we make improvements and fixes.

## Overview

Check out this 2 minute overview to get the big picture of the DoubleLoop Jira app.

{% embed url="<https://www.loom.com/share/13158d1ff7a745a7af4ddca913b771eb>" %}

For more on the value prop, check out the [marketing website for Jira app](https://doubleloop.app/jira-app).

## How to install the Jira app

1. [Login](https://app.doubleloop.app/sign_in) to DoubleLoop or [create your account](https://app.doubleloop.app/sign_up), if you haven't already done so.
2. Import your Jira data into DoubleLoop. Go to the [Jira integration page](https://app.doubleloop.app/settings/integrations/jira) and follow the instructions.
3. To add the DoubleLoop "Business impact" panel to the issue detail view in Jira, click [this link](<https://developer.atlassian.com/console/install/4aa0ef74-fe87-409d-a37d-41f00113c7ba?signature=4496079fec67565eb39c9a2f4d31165eb3db79f06b33489f3e06f12ebf02a84568d3aea68971b2963bbf9cf40ef8e7ff8de169b52efb5f9e1f72713d5d689f93\&product=jira >) and follow the steps.

## How to use the Jira app

After you complete the above installation steps, here's what you can do with it.

#### 1. Add Jira work to your DoubleLoop maps

<figure><img src="https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2FbFGhtZVphE3Vvm7JqPNu%2FCleanShot%202023-04-24%20at%2013.08.24.gif?alt=media&amp;token=19862c88-1287-4804-aa9c-b5db7eef76b4" alt=""><figcaption><p>How to add Jira work to your DoubleLoop map</p></figcaption></figure>

After you complete step 2 in the installation steps above, you'll be able to add Jira work to your map. To do so:

1. Open a map.
2. Click the Jira icon the left menu of tool options.
3. Search for a Jira epic, issue, or initiative.
4. Drag it onto your map and link it with bets or metrics.&#x20;

#### See the business impact panel in Jira

After you complete step 3 in the installation steps above, you'll see the "Business impact" panel appear in Jira for issues/epics/initiatives on your DoubleLoop maps.

Here's what the business impact panel looks like in Jira.

<figure><img src="https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2FH4QXUf2MUEKlDaRCuN4A%2FCleanShot%202023-04-24%20at%2013.15.44%402x.png?alt=media&amp;token=49b92c33-96d6-4fe1-b6a9-b775da28d093" alt=""><figcaption><p>Business impact panel in Jira</p></figcaption></figure>

### What data will display in the business impact panel?

Data from DoubleLoop will display in the business impact panel from nodes that are *directly connected* on the map to the Jira issue/epic/initiative.

<figure><img src="https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2FT9BaySPvBowB0RMHolhh%2FCleanShot%202023-04-24%20at%2013.19.48%402x.png?alt=media&amp;token=2ce85a06-9bfe-484c-8c6d-fe78ff8f4bb1" alt=""><figcaption></figcaption></figure>

## Feedback

What else what you like the Jira app to do? How could it be easier to use? What's confusing about it? Please email/intercom/slack us your thoughts.


# Event fields

Learn about manually recording events in DoubleLoop.

Here's a quick explanation of each event field. All of the fields are optional except for the title, data, and importance.

* **Event title**. The headline that appears wherever the event info is displayed. Example: "Homepage redesign went live."
* **When did the event occur**. The date of the event. Example: the date the product enhancement was released.
* **Importance**. The significance of the event. It determines how prominently the event is displayed in some views.
* **Impact.** When you set the impact for an event, it will appear as an annotation in the timeline on the workstream and all events pages. Positive impact displays in green. Negative impact displays in red.
* **Summary**. A description of the event.
* **Goal / Hypothesis**. When applicable, explain why the change was made. For example: "Our hypothesis is that, by making the button bigger, the conversion rate will increase."
* **Results**. After time passes, you can record the impact of the change. Example: "The conversion rate increased from 2% to 3%.
* **Type**. Record if the change was a fix, enhancement, chore, improvement, etc..
* **URL title.** A call-to-action to learn more about the event. Example: "Watch the demo!"
* **URL.** The URL where you can learn more, corresponding with the URL title.
* **Labels**. Make it easy to find the event later or add the event to a workstream that filters by label.
* **Contributors**. List the people who worked on the change; the PM, engineer, designer, etc. Give props!

##


# Asana integration

## How the date is set in DoubleLoop for Asana tasks

* If there is a start date set in Asana for a task, that will determine the "Happened at" date in DoubleLoop.
* Otherwise:
  * If there is a due date set in Asana for a task, the "end" of the time range is used as the "Happened at" date in DoubleLoop.
  * Otherwise, the "Happened at" date in DoubleLoop is set to the date the Asana task was last modified.

## How the status is set in DoubleLoop for Asana tasks

* If the task is completed in Asana, it's status is set to "Finished" in DoubleLoop.
* Otherwise:
  * If the task has a start date in Asana and the start date is in the past, then the status is set to "Started"
  * If the task has an end date in Asana and the end date is in the past, then the status is set to "Started"
  * If the task does not have a start date or end date or both dates are in the future, then the status is set to "Not started"


# Access settings for maps

Learn how to share public or private maps.

By default, your maps aare private such that login is required to access them. However, you can make them public if you'd like to open access to folks outside your company, like customers.

Here's how each access option works:

| Access option             | When to use it                                                                                                                                                  | How it works                                                                                                                                                                                                                                         |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Private                   | Use it when your view contains sensitive data that would be dangerous to leak outside your company.                                                             | <p>Only users who are logged into DoubleLoop can access it.</p><p>The page will not be listed by search engines.</p>                                                                                                                                 |
| Private with token access | Use it when you want to make it easy for a select group of stakeholders or customers to access it without logging in, but you don't want it to be fully public. | <p>To load the page, you need the correct token in the URL. If your URL with the token gets in the wrong hands, let us know and we'll generate a new token for you to expire the old links.</p><p>The page will not be listed by search engines.</p> |
| Public                    | Use it when you want to make your page accessible without login to your customers or the general public.                                                        | <p>Anyone with the link can access it.<br><br>Search engines can list it.</p>                                                                                                                                                                        |


# Automated Slack reports

Learn how to send reports of your metrics and work to Slack.

With DoubleLoop, you can push reports of metric performance and work progress to Slack automatically on a regular basis. It's a great way for teams to stay focused on the metrics that matter and keep stakeholders in-the-loop.

## Example Slack Report

<figure><img src="https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2FuQXsVTJjn1xqC2fuQR3v%2FCleanShot%202023-11-15%20at%2015.13.13%402x.png?alt=media&amp;token=0fb67999-473c-457e-9dda-56eadb9a3161" alt=""><figcaption></figcaption></figure>

## Setup instructions

1. On the [Slack integration page](https://app.doubleloop.app/settings/integrations/slack), click "Connect."
2. Go to one of your strategy maps.
3. Open settings.
4. Under Slack channel, type the name of the channel that you would like to send reports to and select it.
5. Save you settings.

After you've set it up, reports will be sent to Slack every week on Friday.

## Support

If you need any help with the integration or have ideas for enhancing it, please email us at <support@doubleloop.app>.


# Company Map Generator (AI assistant)

Learn how to use DoubleLoop's AI assistant for generating strategy maps based on public or proprietary documents.

Note: this feature is only open to users in our beta group. To request access contact <support@doubleloop.app>.

## Overview

The purpose of our Company Map Generator is to enable companies to quickly map the strategy of their prospects or customers, or even their own strategy.

For example, based on a public investor presentation and off-the-shelf marketing materials, you can generate a map like this:

<figure><img src="https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2FflCH2drVaqhKB5aKaKf4%2FCleanShot%202024-08-21%20at%2009.49.32.png?alt=media&amp;token=52183d99-afb3-46a3-88f3-8b7466d2e641" alt=""><figcaption><p>Click <a href="https://app.doubleloop.app/strategy/4053/map">here</a> to see actual map in DoubleLoop.</p></figcaption></figure>

## Use cases

We've seen companies use this tool for combinations of these purposes:

* Sales teams generate maps of their prospects in the sales process.
* Customer success teams generate maps of their current customers to show how they deliver value.
* Product teams generate maps of their customers to inform their product strategy and roadmap.
* Product teams generate maps of their own company's strategy to illustrate how their work fits into the big picture.

## Demo video

{% embed url="<https://www.loom.com/share/d0ff7c0b17b34aa7b46f9537c5b25785>" %}

## Instructions

### Setting the stage

1. Login at <https://app.doubleloop.app/>.
2. Click "Create map"
3. Use the "[Corporate Objectives Template](https://app.doubleloop.app/playbooks/corporate-objectives-template)"
4. Wait for the map to fully populate on the canvas. It takes about 45 seconds. When done, you should see this:

<figure><img src="https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2Fc0RXcjMjZUEl1GoFLze7%2FCleanShot%202024-08-21%20at%2011.57.40%402x.png?alt=media&amp;token=c5fd6e62-3de1-41b3-8db9-b2e92fd3d1f5" alt=""><figcaption><p>Corporate objectives template</p></figcaption></figure>

### Use the AI assistant to populate the template

#### Synthesize the strategy from available documents

1. Click the head icon in the bottom toolbar to open the AI assistant menu.![](https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2Fdv1jwOBxzLUQianpJXc2%2FCleanShot%202024-08-21%20at%2011.59.24%402x.png?alt=media\&token=090c1245-b6c4-40cb-a030-ea94857c3722)
2. Select "Corporate Strategy Generator"
3. Click "Start a new conversation"
4. Type "Go" and submit the message. It will take a few seconds for the first message to process.
5. When prompted "What company are you focused on?", enter the name of the company you want to map the strategy for (e.g., Target) and submit.
6. When prompted "What materials should I use for the analysis?", upload PDFs, .txt documents by clicking the upload icon, or paste text directly into the message and submit. You must enter some text like "Here ya go" to submit the message. Notes/tips:
   1. The AI assistant can't access URLs, so you need to provide the content directly.
   2. For the content, we recommend PDFs of earning reports, earning presentation transcriptions, strategy decks, CEO interviews, company websites, or company release notes.
7. The AI assistant should give you a summary of what you provided to help you feel confident that it can analyze the content.
   1. If the descriptions of the content look suspiciously generic, ask it to try again to summarize or upload new files.
   2. If it looks good, tell it to "proceed."
8. Now the AI assistant will give you a text synthesis of the strategy. This allows you to adjust the strategy summary before you populate the map. You can adjust it however you want; e.g., by telling the AI to focus on a specific part of the strategy (e.g., "Focus on digital strategy") or go deeper into one area (e.g., "One of the objectives should be about AI"). When you're happy with it, tell it to "proceed."

<figure><img src="https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2F6Jm3HOiD5iIxF01i1DgZ%2FCleanShot%202024-08-21%20at%2012.46.43%402x.png?alt=media&amp;token=8b9068f3-7fb6-49e9-93d0-109b2ac5f3f2" alt="" width="375"><figcaption><p>Excerpt of a strategy synthesis.</p></figcaption></figure>

9. Now we're ready to update the map... keep reading in the next section.

#### Update the map with the strategy

This section gets a little technical in running through the process of updating the map. In the future, we want to better hide "how the sausage is made."

10. The AI assistant should provide you with a list of all the "template spaces" from the map. There should be 89 of them and it should look like this: <img src="https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2Fri8r1QD5BpTNrdPFutuJ%2FCleanShot%202024-08-21%20at%2012.28.49%402x.png?alt=media&amp;token=5a188823-137e-428e-a0f2-3deb9083ef16" alt="" data-size="line">
    1. If it doesn't look right, ask it to try again.
    2. If all looks good, say "Proceed"
11. Now the AI assistant will use the strategy you generated before to populate each template space on the map. It should look like this: <img src="https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2FVlv5xPt1QPhRwpTMpsvH%2FCleanShot%202024-08-21%20at%2012.34.43%402x.png?alt=media&amp;token=42c39140-d047-429e-ad9a-12a601099f35" alt="" data-size="line">. You can probably just trust it and say "proceed". If something goes wrong down the road, you can come back to this step to figure out what happened.
12. Now the AI assistant will populate your map! After a bit of time, you should see the template disappear and a new map with the strategy content re-appear. Wait until you see all the connectors on the map appear (it might look like it gets stuck, but wait for it...)

<figure><img src="https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2Fsvx459NmeNS8It3ovUNn%2FCleanShot%202024-08-21%20at%2012.47.48%402x.png?alt=media&amp;token=bed0d201-8d9a-4ae3-b56f-ea63c278e67c" alt=""><figcaption></figcaption></figure>

#### Make adjustments

13. Remove any objectives, initiatives, or metrics that you want. Sometimes you will see "Not needed" or a metric that you think is goofy. <img src="https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2F1wzv0E7k5LdPeu0R5Y8x%2FCleanShot%202024-08-21%20at%2012.40.24%402x.png?alt=media&amp;token=bc78b90a-6733-46c2-bfef-4e095ecdd460" alt="" data-size="line">
14. Make any other changes you want; e.g.:
    1. Rename nodes
    2. Add new stuff
    3. Do whatever you want to the map!

Note: if you think the map is too far off from anything you want to use, it's probably best to start this entire process over. In the future, we want to make it easier to use the AI assistant to tweak the map after it's been generated.

#### Share the map

15. If you want to populate the map with dummy data to simulate what it will look like with real data, click the gear icon in the upper right to open "strategy settings." In that modal, click "Populate metrics random data." After you submit the subsequent form, your metrics will start "lighting up" with dummy data.

<figure><img src="https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2FFE6PAsISYcPIber2inKn%2FCleanShot%202024-08-21%20at%2012.56.32%402x.png?alt=media&amp;token=be8d616d-685d-45ad-a3aa-9485f82f6ad8" alt=""><figcaption><p>Map lit up with dummy data</p></figcaption></figure>

15. Also in the "Strategy settings" modal, you can change the sharing settings to "Public." Be sure to click "Save" at the bottom of the modal after you do. Then you can share a link to the map.
    1. Note: if you want to share a version of your map with no dummy data, add `?metricData=false` to the end of the URL like this: <https://app.doubleloop.app/strategy/4385/map?metricData=false>. When you're in this mode, you can light up the map with data by clicking "show metric data" in the toolbar.<img src="https://2649897075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHHueOqTqo2O69VPdaM%2Fuploads%2F6WEz39TcSxgv1wqcOCwE%2FCleanShot%202024-08-21%20at%2012.54.24%402x.png?alt=media&amp;token=4169bced-d623-41cd-ac81-69543baa0d1a" alt="" data-size="line">
16. Of course, the best way to share the map is probably over a screen share in a meeting with your team or customer. Edit the map together! It's just a jumping-off point.

## How you can take this further

1. Map your value proposition to the map (see the screenshot at the very top).
2. Map "bets" to the map.
3. Create sub-maps to go deeper into certain areas.
4. Work with the DoubleLoop to customize this process to your specific value pop and customer profile.

## Need help?

Contact <support@doubleloop.app>.


