Currently, I have custom events implemented in source code and I would like to migrate them on GTM. Is there any option to migrate all those custom events rather than doing it manually (implement all custom events in GTM again from scratch)?
No, there's definitely no such option due to how many ways custom events can be implemented.
They should be carefully migrated manually. Preferably by someone with solid front-end experience or in collaboration with FE developers.
Related
Currently working on a CMF for a web platform that uses firebase, Firebase Analytics and AdSense. However firebase's docs on consent and user privacy for the web are either missing a lot of stuff or the api doesn't have granular control over it.
The app config property I'm referring to is not explained by The settable config flag for GDPR opt-in/opt-out. Can anybody explain what it does and controls? And, possibly out of the scope of this question, how to granularly enable and disable data collection on specific firebase services and the related AdSense? Of course gtag commands would solve this but as I'm using gtag via FB Analytics, it's possibly not exposed(certainly not in the docs) and I don't think loading the gtag again is a good solution, if it'd even work.
I went through the documentation provided here but couldn't find any code to implement google tag manager in gmail addon and to push data to GTM event. I also tried finding a way to implement google tag manager script provided at Quick Start Guide but nowhere found a way to implement the same in gmail addon (apps script).
Any solution would be appreciated.
Workspace Addons do not expose the browser DOM so there is no standard way for you to load/embed a GTM container snippet using the typical methods.
When you embed a GTM container snippet in a webpage it loads a series of tag scripts, so you'd need to find some way to emulate that from server-side GAS.
As a starting point, you can fetch the gtm.js script for your container by going to:
https://www.googletagmanager.com/gtm.js?id=GTM-xxxxx
You could then try embedding that script in your GAS project but then you'd have to refactor that code to work from server-side GAS, which does not natively support the DOM methods common to client-side JavaScript that runs inside a browser.
You might be able to create your own polyfills (or leverage existing libraries from a resource like NPM), but you'd have to do a lot of work mapping DOM code to their Apps Script equivalents where possible.
Looking for insight into how I can programmatically track my code version (aka release version 1.0,1.1,1.2 etc) within google analytics. Currently I manually mark annotations but since annotations can't be added via API perhaps there is another mechanism? Looking for insight into how others have done this. The business case would be allowings other to see how different releases affects traffic/segments.
Reposted From Google Analytics Forum:
Hi All, Just wondering how others have tracked application versions programatically. Currently every time we release code we go into google analytics (manually) and create an annotation with the release number. This allows our GA users to see when we released and cross-reference the release to any potential changes in traffic/conversion/etc. There is currently no way to programmatically create that annotation (https://code.google.com/p/analytics-issues/issues/detail?id=53) however how do others track this. Perhaps there is a recommended way or every time you send a GA event you include the application release number, which we have hidden in the HTML of the site.
https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!msg/analytics/COIXYUCgAXg/nfVctltmDj8J
You can use a custom dimension and push the release version into it.Later you can use the custom dimension to segment the user based on ur requirements
I have an ASP.NET Razor / Web Pages site that I need to integrate with PayPal Express Checkout. Edit: this integration requires more than just a simple PayPal-generated button, e.g., I need to dynamically set the price, item description, tax etc.
I am quite new to both Web Pages and PayPal integration so would like to ask what the preferred approach would be.
So far, I have found there are these options:
Use PayPal Helper for WebMatrix
Just read the PayPal spec and create a form with hidden fields etc.
Use some of the NuGet packages from PayPal
Inspire in some custom code like this one
No. 1 is probably some outdated code (both the release date and recent reviews suggest that), no. 2 will certainly work but I'll be on my own, I'm hoping that no. 3 would be the best answer but there are many of those NuGet packages and I haven't found any good examples yet, and 4 is an option if no other works.
Any suggestions? The goal is to have a simple form, below it my custom "Pay Now" button (preferably; could be also a PayPal-provided button) and when user clicks it, the website should redirect him to PayPal, process the payment notification / approval etc.
I realize this question is old, but if you're looking for SDKs provided by PayPal that support Express Checkout, then you have the following two options:
PayPal .NET SDK
This SDK (formerly known as the "RestApiSdk") is built on the newer PayPal REST APIs and provides support for Express Checkout through the Payments API. All API calls use an OAuth token for security and the calls (and associated code) are a bit cleaner than its Classic counterpart. While some aspects of the REST services are still not quite up to par compared to Classic (e.g. Subscriptions), the Payments portion of the REST APIs is mostly at parity with Classic. Moving forward, this is the SDK that PayPal will be investing in and improving, so it's recommended that any new integrations use this SDK.
Recently, the .NET SDK repo on GitHub was updated with a Wiki that should hopefully make it easier to get started using the SDK. Also, a lot of work has also been put into the included samples project to help show how to use SDK with various use cases. And if there's a use case that's missing or needs better/more explanation, definitely don't hesitate to let me know on there. :)
PayPal Classic Merchant SDK
The Merchant SDK has been around for awhile and all the classes are auto-generated from PayPal's publicly-available WSDL schema files. While it provides support for every Express Checkout-related feature, using it is a bit more cumbersome than the REST-based SDK.
PayPal is no longer actively supporting the Merchant SDK and will only be providing bug fixes when necessary. For this reason, PayPal doesn't recommend using this SDK for new integrations.
If you find a feature that you enjoy using in this SDK that isn't available in the REST counterpart, please let me know here or on GitHub. One issue we've noticed for people looking to switch is the REST API does not provide payment history details for payments made via Classic calls. The PayPal SDK team is currently looking into ways this support can be added to the REST-based SDKs to make it easier for developers to make the transition.
The only option you have is to call rest api from asp.net web pages.
You can find the source code of rest api at following places.
https://github.com/paypal/rest-api-sdk-dotnet
http://paypal.github.io/sdk/
Borek,
if you just want PayPal Express Checkout the easiest way to do it is to simply create a PayPal "Buy It Now" button. You don't need to code anything.
You can find out how to do it here https://developer.paypal.com/docs/classic/paypal-payments-standard/ht_create-pps-buttons/ but the basic steps are:
Create the button inside PayPal.
Copy the button code inside PayPal.
Paste it into your website/email whatever.
Hope that helps!
The Sitecore Calendar Module doesn't have the features that we want: recurring events, multiple calendar integration, event notifications.
My team is looking at 3rd party solutions and is thinking seriously about JQueryUI front-end, in-house business layer, and Google Calendar API back-end. Before jumping in with the Google solution, what other implementations have teams been working on?
We are rolling our own using similar technologies, however, we are using the Sitecore tree as a data store and FullCalendar as the front-end.
We decided on using the tree so that we could utilize Sitecore's pipeline model to schedule tasks, reminders, and automate publish/un-publishing of events. Plus it is a familiar environment for our content authors.
DDay.iCal takes care of .ICS generation pretty well.
One hurdle was handling timezones properly in Sitecore which automatically assumes the timezone of the CM server. We ended up creating a custom Droplist field that pulls in Windows' timezones in the form of TimeZoneInfos.
Whatever you decide, I'm interested to hear how things progress. Best of luck!
I recently grabbed the Sitecore Calendar module Shared Source project and complied it against the Sitecore 7.0 DLLs. I got it running but the Javascript library it uses (Prototype.js) conflicts with jQuery 1.9.1 which we use quite heavily in our website projects.
I have since given up on the Sitecore Calendar and am investigating integrating with either FullCalendar or DayPilot. Can you provide any update on progress with integrating these controls? Dare I ask... is any GitHub code samples available so that we too don't need to re-invent this wheel?
As an aside, I am dissapointed in Sitecore R&D for not offering better 'out of the box' solutions for this. I'm finding their CMS is great for ground up "empty canvas" website projects but not for portal type projects and I'm trying my best not to resort to a SharePoint solution.