Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added support for CD and CV to Matomo Tag and Variables #201

Open
wants to merge 1 commit into
base: 4.x-dev
Choose a base branch
from

Conversation

MichaelRoosz
Copy link

@MichaelRoosz MichaelRoosz commented Nov 6, 2019

  • Added support for Custom Dimensions and Custom Variables into the Matomo Tag
  • Added support for Custom Variables into the Matomo Variable

I think some tests still need to be adjusted, I will update the PR to fix them.

Requires matomo-org/matomo#15125.

…omo Tag

Added support for Custom Variables into the Matomo Variable
@@ -137,7 +137,84 @@ public function getParameters()
}
return $value;
};
})
}),
$this->makeSetting('customDimensions', array(), FieldConfig::TYPE_ARRAY, function (FieldConfig $field) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MichaelHeerklotz Not 100% sure I understand why they are also needed in the Tag and not just in the variable?

Copy link
Author

@MichaelRoosz MichaelRoosz Nov 7, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tsteur As I understand it, triggering Custom Variables or Dimensions in a Tag gives more flexibility, and allows having multiple tags with different Custom Vars/Dims while using the same Matomo Config Variable. I am not a power user yet, but my colleagues requested this feature.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK. In case you can find out just also for our understanding: Why is it better to have multiple tags over multiple configurations? Of course when you have multiple variables then it means you still need multiple tags so it be maybe a bit more work using the variables. Just wanting to avoid suddenly having heaps of configurations in the tag that are also in the variable (and more and more coming in their over time) and confusing users because there are two ways to do things. I can kind of see it though for custom dimensions and custom variables as they might be in PAGE/ACTION scope and the variable should maybe be used mostly for VISIT scope.

Wonder if we should explain this in the description that these are maybe mostly meant for custom dimensions in scope action/page?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I think so, too. I think it makes sense having them both in the tag and the variable because it makes sense if they are of scope page.

Some explantion would help for sure.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should I add some explanations? Is there anything else missing for a merge?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nothing else missing to merge but the explanation. This will help users to know when to use what eg MatomoConfig custom dimensions vs Matomo tag custom dimensions.

We'll need to fix the tests then but can do this after merging.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MichaelRoosz any chance you could add the explanation as discussed so we can merge?

@sgiehl sgiehl changed the base branch from master to 4.x-dev February 7, 2020 14:54
@diosmosis diosmosis added this to the Current sprint milestone Apr 12, 2021
@innocraft-automation innocraft-automation removed this from the Current sprint milestone Jan 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants