Your debug log shows no problems with Pi-Hole that keeps it from blocking ads. In particular, this section of your debug log shows that it is working properly resolving DNS queries.
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] adwarehitman.com is 0.0.0.0 via localhost (127.0.0.1)
[✓] adwarehitman.com is 0.0.0.0 via Pi-hole (192.168.0.13)
[✓] doubleclick.com is 18.104.22.168 via a remote, public DNS server (22.214.171.124)
This problem is likely due to another DNS path to a third party DNS either on your router or client(s). With two DNS entries, the DNS traffic will go to both; some will go to Pi-Hole and some will bypass the Pi-Hole.
A quick way to check this is to use a client (desktop or laptop is usually a good choice), and assign that client with a manual DNS of Pi-Hole IP and nothing else. Clear the DNS cache on that client and then tail the pihole.log (Web Admin GUI > Tools > Tail pihole.log) and see if the traffic from that client is getting to the Pi-Hole.