-
Notifications
You must be signed in to change notification settings - Fork 47
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
HttpRequest for trackerUrl and siteId #88
Comments
I had the same issues with a different matomo package, but I think they do quite the same. See EmmanuelRoux/ngx-matomo-client#31 for more information |
@aicokleinovink: thank you very much for your answer. Unfortunately this does not work for my project. But I am eagerly waiting for the implementation mentioned here: EmmanuelRoux/ngx-matomo-client#54 and would then switch to this repo. |
Hi |
@lousley, I guess you may want to fetch the complete configuration for the module from a distant server, not just the scriptUrl and siteId? |
@Arnaud73 yes that would be nice |
Running into the same issue; please support dynamic configurations :). For inspiration, you can take a look at the Deferred (asynchronous) configuration that this alternative Matomo library provides: https://github.com/EmmanuelRoux/ngx-matomo#deferred-asynchronous-configuration |
Is there any progress on this issue? |
Hi there
I am currently migrating from matomo 0.1.4 to 1.0.1. In my project we get the trackerUrl and the siteId via an HttpRequest. So far i could solve this with the MatomoInjector. How can I integrate this into the forRoot? Is there any idea?
The text was updated successfully, but these errors were encountered: