As long as you've set up paid search detection rules, the segment rule 'paid search = paid' should work great.

Hi Sri,It was an interesting question that you have raised. Just for your information there is "No" possible way to delete your report suite ID from the Adobe analytics, rather than you can hide the report suite from the Company Settings if you have Admin privileges. But again make sure those hidden report suites still continue to be collect data and also billed accordingly.As per the article, that you have linked in the post might be the options from Adobe Target - Adobe Search/Promote product ...

There is no "one-size-fits-all" solution for this. Your solution is unique to how your site is setup. If you want some pointers, you will need to provide details about how your site is setup. For example, does your form have a unique URL the visitor has to go to? Or is it some button you click and you get an overlay on a page? Is it embedded as an iframe on your site? Same with the "thank you" / confirmation page. But also, do you care about tracking only submit attempts (as in, user clicks the ...

It looks like you're already capturing event40 on click of any star, I would just use js to determine which n-th chld (star) was clicked, or add .star-1, .star-2, .star-3... as classes on each star for exact determinationThen once you know which star, pipe that into an eVar or prop on the event40 rule.specifically for DTM, you need to determine business case. Are you collecting on click (event40), or on submit of the form. then you would create a data element to reference in the event rules. The...

It shouldn't matter that your webpage is built on Sharepoint. If you're seeing the beacon in the debugger (or better the network tab), the data is being sent.With that said, we do need to make sure you are sending your beacon to the correct location. Have you verified you are using the correct tracking server in your implementation? What about report suite? Finally, have you verified the report your running in Analytics is set to run on the same report suite you've been sending the data to?

Depending on a number of other factors, e.g. other elements within your element, or other javascript event handler configurations, you may need to alter other settings in your rule.Two of the most common settings to try toggling are:Apply event handler directly to element - By default, DTM uses event delegation for DOM element event handling. It may be possible you have some other javascript code attached to the element (or a child of it) that is preventing the event from bubbling up to the bod...