# Assisted conversions

**URL:** https://community.piwik.pro/t/assisted-conversions/3879
**Category:** Data collection and tags
**Created:** [April 11, 2024, 10:51am UTC](https://community.piwik.pro/t/assisted-conversions/3879 "2024-04-11T10:51:47Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![Katie\_Beebole](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/katie_beebole/32/3308_2.png) [@Katie\_Beebole](https://community.piwik.pro/u/Katie_Beebole)
#### Post date: [April 11, 2024, 10:51am UTC](https://community.piwik.pro/t/assisted-conversions/3879/1 "2024-04-11T10:51:48Z")

</div>

I’d like to know the best way to set up an assisted conversion goal. I need to know the # of people who sign up for a free trial/demo but who FIRST enter via our blog. What would be the best way to do this?

---

<div class="post-metadata">

### Author: ![anthonybartczak](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/anthonybartczak/32/2430_2.png) [@anthonybartczak](https://community.piwik.pro/u/anthonybartczak)
#### Post date: [April 11, 2024, 12:19pm UTC](https://community.piwik.pro/t/assisted-conversions/3879/2 "2024-04-11T12:19:30Z")

</div>

Hi @Katie_Beebole,

If a sign up happens in the same session, you will probably want to use a funnel with a page view on the landing page as the first step and sign up goal conversion as the last one.

If the sign up can happen in a different session (not the current one), I think that the attribution report might be the way to go:  
[Attribution report | Piwik PRO help center](https://help.piwik.pro/support/reports/attribution-report/)

([perhaps this thread might be relevant](https://community.piwik.pro/t/piwik-attribution-event-sent-from-bq-database-always-direct-direct/3715/3))

---

<div class="post-metadata">

### Author: ![Elena\_Benito\_Ruiz](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/elena_benito_ruiz/32/1823_2.png) [@Elena\_Benito\_Ruiz](https://community.piwik.pro/u/Elena_Benito_Ruiz)
#### Post date: [April 11, 2024, 4:50pm UTC](https://community.piwik.pro/t/assisted-conversions/3879/3 "2024-04-11T16:50:48Z")

</div>

Hi @anthonybartczak Katie’s colleague here 🙂  
The attribution report is more to analyze acquisition channels and compare data depending on attribution model. To us, the blog is not an acquisition channel like organic, ppc, etc, it’s part of the target, the whole domain, conversion can happen in the blog.

It’s not about knowing whether they entered via blog or not, either.

We track clicks on trial and demo CTAs that we place in the blog, but also across the whole commercial site. We have tracking tags and goal for this.

We have a report where we can see how many of those goals happened on blog urls (filtering page url to those containing /blog) and it does show the count of those CTA clicks. I assume this is due to the typical non-direct last interaction attribution to the blog post, correct me if wrongly understood. So it’s counting those clicks that happened on those urls.

But then the blog post could be somewhere else in the customer journey that is not the non-direct last one, say it’s the first, or middle touchpoint once inside our domain, but not the last non direct. I remember we could check direct but also indirect or assisted conversions in Google Analytics (universal, afair) for a given path or set of urls.

---

<div class="post-metadata">

### Author: ![Elena\_Benito\_Ruiz](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/elena_benito_ruiz/32/1823_2.png) [@Elena\_Benito\_Ruiz](https://community.piwik.pro/u/Elena_Benito_Ruiz)
#### Post date: [April 11, 2024, 5:01pm UTC](https://community.piwik.pro/t/assisted-conversions/3879/4 "2024-04-11T17:01:43Z")

</div>

@anthonybartczak  
about the funnel report [Brave Browser - Funnel Blog Test (edit report) - Custom reports - Analytics - Beebole - 11 April 2024 | Loom](https://www.loom.com/share/bf6c5cab46854436baa4298af3dffe5a)

🙏🏻 thank you as always

---

<div class="post-metadata">

### Author: ![anthonybartczak](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/anthonybartczak/32/2430_2.png) [@anthonybartczak](https://community.piwik.pro/u/anthonybartczak)
#### Post date: [April 18, 2024, 10:29am UTC](https://community.piwik.pro/t/assisted-conversions/3879/5 "2024-04-18T10:29:10Z")

</div>

Sorry for a bit of a late response.

So granted you’d like to focus more on the action part (e.g. blog page view) and not the acquisition in context of what happened before a certain conversion, then it sounds like a case for sequential segmenting. Basically having the ability to create multiple event-based conditions (combine multiple steps/events within a session) to filter out sessions.

This one is currently not supported in Analytics but the general improvements to segments are pretty high on the feature request list.

That said, you could try to create a workaround (although it might not fully address your needs) that would push a value to a session custom dimension once someone hits a blog page (or any other key page/interaction). This way you could use this dimension in the attribution report.

Though it might become a bit more tricky if you’d like to look at every single blog page that assisted the conversion because by default the custom dimension will only contain the last tracked value (it won’t become an array if you push another blog post name to it).

---

<div class="post-metadata">

### Author: ![Elena\_Benito\_Ruiz](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/elena_benito_ruiz/32/1823_2.png) [@Elena\_Benito\_Ruiz](https://community.piwik.pro/u/Elena_Benito_Ruiz)
#### Post date: [April 19, 2024, 4:43pm UTC](https://community.piwik.pro/t/assisted-conversions/3879/6 "2024-04-19T16:43:39Z")

</div>

I see @anthonybartczak what I had done is to create a flat table report with dimensions: session entry url, next url, exit url, previous url…and where dimension url is filtered to contain blog and also filtered by session goal containing the one we want to track as well as goal name. Not perfect indeed, or maybe wrong…but wouldn’t ‘next url’ be then a url that assisted?

---

<div class="post-metadata">

### Author: ![anthonybartczak](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/anthonybartczak/32/2430_2.png) [@anthonybartczak](https://community.piwik.pro/u/anthonybartczak)
#### Post date: [April 23, 2024, 7:08am UTC](https://community.piwik.pro/t/assisted-conversions/3879/7 "2024-04-23T07:08:56Z")

</div>

Would you mind sharing the report URL? Either here or in PM. I want to see metrics used and the general “output”.

---

<div class="post-metadata">

### Author: ![anthonybartczak](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/anthonybartczak/32/2430_2.png) [@anthonybartczak](https://community.piwik.pro/u/anthonybartczak)
#### Post date: [April 24, 2024, 11:14am UTC](https://community.piwik.pro/t/assisted-conversions/3879/8 "2024-04-24T11:14:14Z")

</div>

In this case you’d get an event scoped custom report with:

- `session entry URL`  
Entry URL of the session in which this goal conversion happened

- `next page view URL`  
URL of page view event that happened after the goal conversion

- `session exit URL`  
Exit URL of the session in which this goal conversion happened

- `previous page view URL`  
URL of page view event that happened before the goal conversion

- `goal name`  
Name of the goal conversion

- `sessions`  
Amount of sessions that contained a combination of previously listed dimensions with a certain goal conversion

> [@Elena\_Benito\_Ruiz](#):
>
> Not perfect indeed, or maybe wrong…but wouldn’t ‘next url’ be then a url that assisted?

Did you mean `previous page view URL` instead of `next url`? If the answer is yes then I’d say yes - we can say that this page view assisted in the conversion.
